Question 380
After correcting this architecture issue: An organization deploys App-ID rules but keeps unused broad fallback allows indefinitely. Which ongoing control belongs in the runbook?
Explanation
Correct Answer
Schedule periodic usage reviews backed by application-owner signoff. This lowers the risk linked to: Broad cleanup without rule-hit and business dependency analysis can create outages. Verification should show: Allowed business applications remain available while previously unclassified broad traffic is reduced.
Incorrect Answers
Define consistent log retention and correlation fields across enforcement points. This safeguard addresses another situation: Security operations cannot tell which identity-specific zero-trust rule denied a remote user's session. It is less directly relevant than the control for: Broad cleanup without rule-hit and business dependency analysis can create outages.
Review anomalous rule-hit shifts and reassess the asset inventory after changes. This safeguard addresses another situation: A segmented healthcare network is deployed but nobody measures whether unauthorized east-west attempts rise. It is less directly relevant than the control for: Broad cleanup without rule-hit and business dependency analysis can create outages.
Audit sensitive-data incidents and refine classifiers with approved test documents. This safeguard addresses another situation: A sanctioned cloud storage service is allowed, but executives can upload sensitive exported customer lists. It is less directly relevant than the control for: Broad cleanup without rule-hit and business dependency analysis can create outages.