Document privileges for running Beats features against secured cluster#7128
Document privileges for running Beats features against secured cluster#7128andrewkroh merged 6 commits intoelastic:masterfrom
Conversation
|
@andrewkroh I've added instructions for loading the dashboards when LS output is enabled (we talked about that a couple weeks ago). There are some bits I'm not sure about, so I've added questions for reviewers. We might be able to simplify the command, but I thought I'd start with all the things and see what you think. |
|
Removed my link because it pointed to an internal document. |
karenzone
left a comment
There was a problem hiding this comment.
Started, but not finished. There's a lot going on here. Looks like it's heading in a good direction
libbeat/docs/dashboards.asciidoc
Outdated
There was a problem hiding this comment.
This should be {beat_default_index_prefix}_internal. There are a few instances of this.
libbeat/docs/dashboards.asciidoc
Outdated
There was a problem hiding this comment.
We don't need set it in this case. I think it only needs to be used when loading the dashboards (setup --dashboards) and a connection to ES is not possible (so it will skip the ES version check).
libbeat/docs/dashboards.asciidoc
Outdated
There was a problem hiding this comment.
We can remove the conditional for auditbeat. It is used with docker quite a bit now.
There was a problem hiding this comment.
kibana_user seems ok. I'm not sure what privileges could be removed.
BTW If the user does not have privileges to .kibana there are no errors anywhere that I can see. But none of the dashboards or the index pattern get installed. Sounds like a bug in ES or Kibana that it does not respond with a 403.
There was a problem hiding this comment.
@andrewkroh Do I need to open an issue for this, or do you plan to follow up?
libbeat/docs/dashboards.asciidoc
Outdated
There was a problem hiding this comment.
I would keep ML. At the moment I think only Filebeat has them, but hopefully more Beats get ML configs soon.
3be46bb to
540b300
Compare
|
@andrewkroh I've updated the topics based on your feedback. Not sure if you've finished your first round of comments, tho. Let me know. There are still a few unanswered questions. |
7b31231 to
89b7c79
Compare
89b7c79 to
bfa4d48
Compare
|
Remaining review todo list:
You can preview the built docs here: https://filebeatsecurityupdates.firebaseapp.com/securing-beats.html |
| { | ||
| "names": [ "{beat_default_index_prefix}-*" ], <1> | ||
| "privileges": ["write","create_index"] | ||
| "privileges": ["read","write","create_index"] |
There was a problem hiding this comment.
What is the read needed for? I can't think of any Beats that would use this. Packetbeat used to a long time ago, but not anymore AFAIK.
There was a problem hiding this comment.
I don't have the reason in my notes. I'll retest to make sure it's not a copy/paste error.
There was a problem hiding this comment.
Confirmed that "read" privilege is not required (tested on metricbeat and packetbeat...I'm assuming that's sufficient).
|
Assuming this passes CI tests, it should be ready to squash and merge. |
elastic#7128) * Document privileges for running Beats features against secured cluster * Add instructions for loading dashboards with LS output enabled * Fix issues identified during review * Remove reviewer notes * Fix privileges on writer role * Add link to security docs
#7128) * Document privileges for running Beats features against secured cluster * Add instructions for loading dashboards with LS output enabled * Fix issues identified during review * Remove reviewer notes * Fix privileges on writer role * Add link to security docs
elastic#7128) * Document privileges for running Beats features against secured cluster * Add instructions for loading dashboards with LS output enabled * Fix issues identified during review * Remove reviewer notes * Fix privileges on writer role * Add link to security docs
Fixes #4826.
Note that this is a quick fix for 6.3. Ideally, we should not be documenting how to create a role; we should point off to the security docs for that. However, our stack-level security docs need more work, so I'm making fixes to the existing content (rather than rewriting) for 6.3. We also need to consider adding more beats-specific built-in roles.
TODO:
UPDATE: I've added the built docs (Filebeat) to firebase to make it easier for you to review them: https://filebeatsecurityupdates.firebaseapp.com/securing-beats.html