Sample question 1 · Identity and Access Management (IAM) Architecture (25%)
Helix Broadcast Networks, a regional media company based in Austin, Texas, produces live sports content and holds exclusive broadcast rights agreements. The company recently deployed a data classification and DLP solution to protect rights-sensitive content metadata and broadcast schedules. During a post-deployment review, the security architect discovers that the IAM audit logging system does not generate alerts or notifications when privileged service accounts — used by automated content distribution pipelines — access Restricted-class broadcast rights data outside of scheduled maintenance windows. A third-party rights management vendor, Orion Rights LLC, has a contractual obligation requiring Helix to demonstrate that access to rights data is logged and that anomalous access generates notifications within 15 minutes. An ethics review by the internal audit committee also flagged that the current alerting configuration sends identity accounting alerts directly to the line manager of the accessing employee, raising concerns about managerial misuse of security alert data for disciplinary purposes outside of a formal investigation process. The security architect must redesign the alert and notification architecture to satisfy the vendor contractual SLA and the ethics constraint simultaneously. As the lead security architect at Helix Broadcast Networks, which audit log alert and notification architecture best satisfies the 15-minute anomalous access notification SLA required by Orion Rights LLC while addressing the ethics concern about managerial misuse of identity accounting alerts?
- A. Configure the SIEM to send anomalous access alerts for Restricted-class rights data directly to the accessing employee's line manager and simultaneously to the vendor's compliance portal, meeting the 15-minute SLA while providing managerial visibility for immediate operational response.
- B. Disable automated alerting for service account access events to avoid the ethics concern, and instead schedule daily summary reports of Restricted-class access activity for review by the security operations team, which can escalate to the vendor within the business day.
- C. Route all anomalous identity accounting alerts for Restricted-class rights data exclusively to the security operations center (SOC) within a 15-minute SLA window, establish a formal escalation procedure requiring SOC analyst review before any alert is shared with line management, and provide Orion Rights LLC with automated notification via a dedicated compliance API feed that confirms alert generation without disclosing employee identity details.
- D. Implement a role-based alert suppression rule that prevents alerts from being generated for service accounts during any hour of the day, and rely on the DLP system's block-and-quarantine actions as the primary compensating control to satisfy the vendor's anomalous access notification requirement.
View answer & explanation
Correct answer: C. Route all anomalous identity accounting alerts for Restricted-class rights data exclusively to the security operations center (SOC) within a 15-minute SLA window, establish a formal escalation procedure requiring SOC analyst review before any alert is shared with line management, and provide Orion Rights LLC with automated notification via a dedicated compliance API feed that confirms alert generation without disclosing employee identity details.
[Domain 4 - Identity and Access Management (IAM) Architecture, Task 4.4 - Architect identity accounting, Area 1 - Determine accounting, analysis, and forensic requirements] Core Concept: Architect identity accounting centers on determine accounting, analysis, and forensic requirements as defined in the official (ISC)² ISSAP exam outline. Correct Answer (C): Route all anomalous identity accounting alerts for Restricted-class rights data exclusively to the security operations center (SOC) within a 15-minute SLA window, establish a formal escalation procedure requiring SOC analyst review before any alert is shared with line management, and provide Orion Rights LLC with automated notification via a dedicated compliance API feed that confirms alert generation without disclosing employee identity details. Why the other options are incorrect: Option A: Routing alerts directly to line managers without a SOC review gate perpetuates the ethics violation identified by the internal audit committee; the architecture must structurally prevent managerial access to identity accounting alerts outside of a formal investigation process, not simply add a parallel channel. Option B: Disabling automated alerting for service account access events eliminates the ability to meet the 15-minute contractual SLA and removes a critical forensic detection capability; daily summary reports cannot satisfy a real-time anomalous access notification obligation and represent an unacceptable gap in the identity accounting architecture. Option D: Suppressing all service account alerts eliminates the anomalous access detection function entirely, which directly contradicts the contractual requirement and the forensic accounting obligation; DLP block-and-quarantine actions are preventive controls that do not constitute notification of anomalous access events as required by the vendor agreement.