Question 770
A service principal has CAN MANAGE on all workflows although it needs only one scheduled ingestion job. Which long-term safeguard BEST reduces recurrence?
Explanation
Correct Answer
Periodically review and rotate machine identity privileges. This is the most directly relevant preventive control because an unrestricted automation identity expands the impact of token compromise. A concrete acceptance check is: The principal can run the approved task but cannot edit unrelated jobs. To reduce recurrence: Periodically review and rotate machine identity privileges.
Incorrect Answers
Separate ingestion code paths can reintroduce cleartext after initial cleanup. Here the important technical distinction is that an unrestricted automation identity expands the impact of token compromise.
Removing direct identifiers alone can leave rows re-identifiable from combinations. The reported failure instead depends on this fact: an unrestricted automation identity expands the impact of token compromise.
Row access does not imply permission to see every sensitive field in raw form. That consideration does not remove the current constraint: an unrestricted automation identity expands the impact of token compromise.