IT Cert Ready

(ISC)²

ISSAP

Information Systems Security Architecture Professional

Start practicing

About this certification

ISSAP (Information Systems Security Architecture Professional) is a (ISC)² certification. IT Cert Ready offers 1,761 practice questions with domain quizzes, full mock exams, and detailed explanations. Practice by official domain with 4 blueprint-aligned domains.

Official exam domain weights

Verified blueprint weights from the official exam outline.

  • Domain 1 · Governance, Risk, and Compliance (GRC) · 21%
  • Domain 2 · Security Architecture Modeling · 22%
  • Domain 3 · Infrastructure and System Security Architecture · 32%
  • Domain 4 · Identity and Access Management (IAM) Architecture · 25%

Sample ISSAP practice questions

Preview realistic multiple-choice items from the IT Cert Ready question bank. Expand each answer for the correct choice and explanation—the same format used in domain quizzes and mock exams.

  1. 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.

  2. Sample question 2 · Identity and Access Management (IAM) Architecture (25%)

    Orbitask SaaS, a U.S.-based workforce scheduling platform serving healthcare clients, is undergoing a black-box penetration test required by its HIPAA Business Associate Agreements before a major feature release. The platform uses a federated identity model with SAML assertions from customer identity providers. The security architect has implemented audit logging for identity events but receives a pre-test report from the internal compliance team indicating that log retention is set to 30 days for all identity audit logs. The HIPAA Security Rule requires covered entities and business associates to retain documentation of security policies and procedures for six years, and the organization's own security policy mandates a 12-month minimum retention for audit logs. The architect must redesign the log management architecture to align with regulatory and policy requirements before the penetration test begins. As the lead security architect at Orbitask SaaS, which log management design decision best resolves the conflict between the current 30-day retention configuration, the HIPAA Security Rule documentation requirement, and the organization's 12-month audit log retention policy?

    • A. Retain identity audit logs in hot storage for 30 days for operational use, then archive logs to immutable cold storage for a minimum of 12 months, with cryptographic hash chaining applied at ingestion to ensure log data integrity throughout the retention lifecycle.
    • B. Extend the hot storage retention window to 12 months for all log types, including application, network, and identity logs, to simplify the retention architecture and eliminate tiered storage complexity.
    • C. Retain identity audit logs for 30 days in the SIEM and rely on the customer identity providers to maintain SAML assertion logs for the six-year HIPAA documentation period, distributing retention responsibility across the federation.
    • D. Increase log retention to six years for all identity audit logs immediately, aligning to the most stringent HIPAA documentation requirement and eliminating the need to differentiate between policy and regulatory retention periods.
    View answer & explanation

    Correct answer: A. Retain identity audit logs in hot storage for 30 days for operational use, then archive logs to immutable cold storage for a minimum of 12 months, with cryptographic hash chaining applied at ingestion to ensure log data integrity throughout the retention lifecycle.

    [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 (A): Retain identity audit logs in hot storage for 30 days for operational use, then archive logs to immutable cold storage for a minimum of 12 months, with cryptographic hash chaining applied at ingestion to ensure log data integrity throughout the retention lifecycle. Why the other options are incorrect: Option B: Retaining all log types in hot storage for 12 months is cost-prohibitive and architecturally inefficient; it also fails to address log data integrity requirements, as hot storage is typically mutable and does not provide tamper-evidence guarantees needed for forensic and regulatory purposes. Option C: Delegating retention responsibility to customer identity providers for SAML assertion logs is architecturally unsound because Orbitask, as a Business Associate, cannot guarantee that third-party IdPs will retain logs in a format or for a duration that satisfies HIPAA requirements applicable to Orbitask's own obligations. Option D: Immediately setting all identity audit logs to a six-year retention period conflates the HIPAA documentation retention requirement (which applies to security policies and procedures) with audit log retention, and does not address log data integrity controls or the cost and architecture implications of undifferentiated long-term hot storage.

  3. Sample question 3 · Identity and Access Management (IAM) Architecture (25%)

    Meridian Global Bank, a multinational institution headquartered in Frankfurt with operations across 42 countries, is implementing a zero trust architecture across its hybrid cloud environment. The bank's IAM architecture team has been tasked with designing an identity accounting framework to satisfy simultaneous regulatory obligations under GDPR (EU), FFIEC guidance (US branches), and MAS TRM (Singapore). During a governance review, the Chief Compliance Officer raises a concern: the current logging design captures authentication events at the identity provider layer but does not record downstream resource-access decisions made by the policy enforcement points (PEPs) distributed across cloud workloads. The legal team warns that in the event of a cross-border data exfiltration incident, forensic reconstruction of the access chain would be incomplete. As the lead security architect, you must determine which accounting requirement gap most critically undermines the bank's ability to satisfy forensic and regulatory obligations. As the lead security architect at Meridian Global Bank, which architectural decision best closes the forensic gap identified by the legal team while satisfying multi-jurisdictional regulatory requirements for identity accounting?

    • A. Extend the existing SIEM to ingest authentication logs from the identity provider and apply correlation rules to infer downstream access decisions based on session tokens.
    • B. Instrument each policy enforcement point to emit signed, tamper-evident access-decision records — including subject identity, resource, action, and policy outcome — and forward them to a centralized, jurisdiction-aware log management platform with defined retention tiers.
    • C. Require application owners to manually document access decisions in a governance, risk, and compliance (GRC) tool after each deployment cycle to maintain an audit trail for regulatory review.
    • D. Consolidate all identity events into the identity provider's native audit log and grant regulators direct read access to that system during examinations.
    View answer & explanation

    Correct answer: B. Instrument each policy enforcement point to emit signed, tamper-evident access-decision records — including subject identity, resource, action, and policy outcome — and forward them to a centralized, jurisdiction-aware log management platform with defined retention tiers.

    [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 (B): Instrument each policy enforcement point to emit signed, tamper-evident access-decision records — including subject identity, resource, action, and policy outcome — and forward them to a centralized, jurisdiction-aware log management platform with defined retention tiers. Why the other options are incorrect: Option A: Inferring access decisions from session tokens via SIEM correlation is an approximation, not an authoritative record; it does not produce the signed, attributable access-decision evidence required for forensic reconstruction or regulatory examination, and inference logic can fail when tokens are reused or delegated across services. Option C: Manual post-deployment documentation by application owners is neither timely nor reliable for forensic purposes; it introduces human error, lacks the granularity of individual access events, and cannot satisfy real-time or near-real-time audit trail requirements imposed by FFIEC and MAS TRM. Option D: Consolidating all events in the identity provider's native log omits PEP-level authorization decisions entirely, replicates the same gap the legal team identified, and granting regulators direct system access introduces operational risk and does not constitute a sustainable, architecture-level accounting design.

  4. Sample question 4 · Identity and Access Management (IAM) Architecture (25%)

    Prismvault Entertainment Group, a large multinational media conglomerate based in Los Angeles with operations in the EU and Asia-Pacific, recently classified its unreleased film assets under a four-tier data classification scheme (Public, Internal, Confidential, Restricted). The company is subject to GDPR for EU employee data, CCPA for California residents, and internal IP protection policies. The IAM architecture team is designing the log management framework for the new DLP-integrated identity accounting system. A compliance audit finding revealed that identity-related audit logs are currently retained for only 30 days, which is insufficient for both regulatory compliance and the company's internal forensic investigation SLA of 18 months. Additionally, the legal team has flagged an ethical concern: audit logs capturing creative employees' behavioral patterns could be used for performance monitoring purposes beyond their stated security scope, which conflicts with EU Works Council agreements and GDPR Article 5 data minimization principles. The security architect must design a log retention and governance architecture that satisfies forensic and regulatory requirements without enabling scope creep into HR surveillance. As the lead security architect at Prismvault Entertainment Group, which log management architecture design best balances the 18-month forensic retention requirement, GDPR data minimization obligations, and the ethical constraint against using identity audit logs for HR performance monitoring?

    • A. Retain all identity audit logs for 18 months in a general-purpose SIEM accessible to both the security operations team and HR analytics platforms, and implement a policy-based access control matrix that restricts HR from querying logs without CISO approval.
    • B. Implement tiered log retention with security-relevant identity events (authentication anomalies, DLP bypass triggers, bulk transfers) retained for 18 months in an access-controlled, purpose-limited log repository governed by a formal data use agreement that prohibits HR access, while retaining routine behavioral telemetry for only 90 days in a separate store subject to automated purge.
    • C. Anonymize all identity audit logs at ingestion by replacing user identifiers with pseudonymous tokens, retaining the full dataset for 18 months, and maintaining a de-anonymization key held jointly by Legal and Security to satisfy both GDPR minimization and forensic re-identification requirements.
    • D. Reduce the forensic retention SLA to 90 days to align with the current log retention practice, document the residual risk in the risk register, and implement real-time DLP alerting as a compensating control to reduce dependence on historical log analysis.
    View answer & explanation

    Correct answer: B. Implement tiered log retention with security-relevant identity events (authentication anomalies, DLP bypass triggers, bulk transfers) retained for 18 months in an access-controlled, purpose-limited log repository governed by a formal data use agreement that prohibits HR access, while retaining routine behavioral telemetry for only 90 days in a separate store subject to automated purge.

    [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 (B): Implement tiered log retention with security-relevant identity events (authentication anomalies, DLP bypass triggers, bulk transfers) retained for 18 months in an access-controlled, purpose-limited log repository governed by a formal data use agreement that prohibits HR access, while retaining routine behavioral telemetry for only 90 days in a separate store subject to automated purge. Why the other options are incorrect: Option A: Storing all logs in a SIEM accessible to HR analytics platforms — even with approval-gated access controls — creates an architectural pathway for scope creep and does not satisfy GDPR purpose limitation at the data architecture level; policy-based controls alone are insufficient when the underlying data store is shared. Option C: Pseudonymization at ingestion satisfies some GDPR obligations but does not address data minimization for routine behavioral telemetry that has no forensic value; retaining the full behavioral dataset for 18 months under pseudonymous tokens still constitutes excessive retention of personal data under GDPR Article 5(1)(e) and does not resolve the HR surveillance ethical risk. Option D: Reducing the forensic retention SLA to match an inadequate current practice accepts a known compliance and forensic gap rather than architecting a solution; documenting residual risk does not fulfill the architect's obligation to design a log management framework that meets established forensic and regulatory requirements.

  5. Sample question 5 · Identity and Access Management (IAM) Architecture (25%)

    Solaris Basin Energy (SBE), a large offshore oil and gas platform operator headquartered in the Gulf Coast region, uses a centralized identity provider to manage access for approximately 340 remote operations vendors across its distributed control system (DCS) network. SBE's internal audit team recently completed a log management review and found three critical gaps: (1) audit logs from DCS historian servers were retained for only 30 days due to storage constraints, well below the 90-day online and one-year offline retention mandated by SBE's own security policy and applicable FISMA moderate baseline controls; (2) log integrity verification was performed manually and inconsistently; and (3) no automated alerting existed for anomalous identity events such as after-hours privileged logins or bulk data exports by vendor accounts. The security architect must present a remediation architecture to the executive steering committee that includes measurable improvement metrics. Which architectural approach should the lead security architect recommend to close all three log management gaps while establishing metrics that demonstrate continuous improvement to the executive steering committee?

    • A. Procure additional on-premises storage for DCS historian servers to extend local log retention to 90 days, configure manual integrity checks on a weekly schedule, and task the SOC with reviewing vendor account activity reports each month.
    • B. Implement a tiered log management architecture with automated forwarding from DCS historian servers to an immutable, centralized log repository that enforces policy-defined retention tiers (90-day hot, 12-month warm), deploy cryptographic hash chaining for log integrity verification at ingest, define alert rules for anomalous identity events (after-hours privileged login, bulk export thresholds), and establish KPIs — including log completeness rate, mean time to alert on anomalous identity events, and retention compliance percentage — reported quarterly to the steering committee.
    • C. Deploy a user and entity behavior analytics (UEBA) platform trained on vendor baseline activity to detect anomalous identity events, and configure the platform to archive flagged events for 12 months, addressing the alerting and retention gaps simultaneously through the analytics tool.
    • D. Renegotiate vendor contracts to require vendors to maintain their own session logs and submit monthly access reports to SBE, reducing SBE's internal log storage burden while shifting forensic accountability to the vendor organizations.
    View answer & explanation

    Correct answer: B. Implement a tiered log management architecture with automated forwarding from DCS historian servers to an immutable, centralized log repository that enforces policy-defined retention tiers (90-day hot, 12-month warm), deploy cryptographic hash chaining for log integrity verification at ingest, define alert rules for anomalous identity events (after-hours privileged login, bulk export thresholds), and establish KPIs — including log completeness rate, mean time to alert on anomalous identity events, and retention compliance percentage — reported quarterly to the steering committee.

    [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 (B): Implement a tiered log management architecture with automated forwarding from DCS historian servers to an immutable, centralized log repository that enforces policy-defined retention tiers (90-day hot, 12-month warm), deploy cryptographic hash chaining for log integrity verification at ingest, define alert rules for anomalous identity events (after-hours privileged login, bulk export thresholds), and establish KPIs — including log completeness rate, mean time to alert on anomalous identity events, and retention compliance percentage — reported quarterly to the steering committee. Why the other options are incorrect: Option A: Extending local storage to 90 days addresses only the online retention gap and does not meet the one-year offline retention requirement; weekly manual integrity checks remain inconsistent and unscalable; monthly SOC reviews are reactive and do not constitute automated alerting or produce the structured metrics required for executive reporting. Option C: A UEBA platform addresses anomalous identity event detection and can archive flagged events, but it does not provide comprehensive log retention for all identity events — only those flagged as anomalous — leaving the retention compliance gap and log integrity verification gap unresolved for the full log population. Option D: Shifting forensic accountability to vendors through contractual log submission does not satisfy SBE's own security policy or FISMA baseline controls, which require SBE to maintain authoritative, tamper-evident logs under its own control; vendor-submitted reports cannot substitute for an architect-controlled, integrity-verified log pipeline.

ISSAP exam prep FAQ

What is the passing score for the ISSAP exam?
Passing scores for ISSAP are set by (ISC)² and can change between exam versions. Check the latest official exam outline on the (ISC)² website for the current passing standard.
How many questions are on the ISSAP certification exam?
Official ISSAP exam length and item types are defined by (ISC)². Review the current exam blueprint for the latest question counts and timing.
How do domain quizzes help with ISSAP exam prep?
Domain quizzes on IT Cert Ready let you practice ISSAP one blueprint domain at a time across 4 official exam domains. You get immediate feedback, detailed explanations, and can revisit weak areas before taking a full timed mock exam.
How many ISSAP practice questions are on IT Cert Ready?
IT Cert Ready includes 1,761 published ISSAP practice questions with domain quizzes, full-length mock exams, and answer explanations mapped to the official outline.