Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding the reader role to, eventually replace the connector role, and adhere to the azure concept of reader and responder.
Up until disrupt, we had two SAP ABAP roles we used to as templates to be assigned to the users our agents used to retrieve data from SAP:
/MSFTSEN/SENTINEL_AGENT_BASIC- for systems up to SAP version 7.4
/MSFTSEN/SENTINEL_CONNECTOR- for systems versions 7.4 and higher
We are now switching the roles to be these (still testing):
/MSFTSEN/SENTINEL_READER- “Sentinel for SAP agent- read only”.
/MSFTSEN/SENTINEL_RESPONDER- “Sentinel for SAP agent- read and respond to threats”.
The logic behind this is to simplify the user experience, and match the sentinel permissions concept of contributor, reader, responder etc.
The new Reader role merges all authorizations from the two legacy roles.