- Notifications
You must be signed in to change notification settings - Fork 508
docs!(beyondinsight_password_safe): Refresh readme, move variable #15327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs!(beyondinsight_password_safe): Refresh readme, move variable #15327
Conversation
Follow the documentation guidelines from the developer docs and template structure from elastic-package. https://www.elastic.co/docs/extend/integrations/documentation-guidelines https://github.com/elastic/elastic-package/blob/89b34ec09f562b2c1c921ba4b465b6ef96ea47de/internal/packages/archetype/_static/package-docs-readme.md.tmpl
52c5f73 to c49ae98 Compare | Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
BREAKING: Move enable_request_tracer to the data stream level. Cleanup some variable descriptions. Add url_allowed_schemes to urls type variables. Set a more concise title and description on the data streams.
c49ae98 to 3873613 Compare There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestions/queries only.
| | ||
| ## Data Streams | ||
| The BeyondInsight and Password Safe integration enables real-time monitoring of | ||
| privileged account access, session recordings, and password checkout patterns to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
| The BeyondInsight and Password Safe integration enables real-time monitoring of | ||
| privileged account access, session recordings, and password checkout patterns to | ||
| help security teams maintain compliance and quickly identify potential privilege | ||
| abuse through BeyondTrust's Just-in-Time (JIT) privileged access management capabilities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "JIT" acronym is not referred to anywhere else. Does it need to be introduced here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not necessary. ba3e75b
| type: text | ||
| title: Interval | ||
| description: Data for all assets will be refetched at this interval. | ||
| description: Data for all assets will be refetched at this interval. The supported time units are "s", "m", "h". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not specific for here, but it's always troubled me that we order these in ascending magnitude. Why? In colloquial English (in my dialect at least) this is not the conventional order.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That does seem more natural.
| show_user: false | ||
| default: "2160h" | ||
| description: How far back to pull BeyondInsight user audit events from the BeyondInsight user audit API(90 days). Supported units for this parameter are h/m/s. | ||
| description: How far back to pull BeyondInsight user audit events from the API. The supported time units are "s", "m", "h". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/pull/collect/g?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| … with the exception that the policy tests need to be examined/updated for the new locations. |
34a7fc0 to 742d81f Compare | Policy tests were failing because I didn't move the |
💚 Build Succeeded
History
|
|
| Package beyondinsight_password_safe - 0.12.0 containing this change is available at https://epr.elastic.co/package/beyondinsight_password_safe/0.12.0/ |




Proposed commit message
Checklist
changelog.ymlfile.Related issues
References
Screenshots