Practice Exams:

Governance & Compliance

IAPP AIGP: Building an AI Risk Register

An AI risk register should help teams decide what to change, not become a catalog of everything that could theoretically go wrong with artificial intelligence. The most useful entries connect a concrete scenario to an affected objective, owner, evidence, control plan, and residual exposure. If a risk cannot influence a design, approval, monitoring threshold, contract, or operating decision, the register is probably too abstract. Home/IAPP/IAPP AIGP: Building an AI Risk RegisterIAPPPublished October 7, 2026On this pageWrite risks as scenarios with consequencesSeparate inherent and residual exposureUse a small, explicit scoring modelConnect…

Read More

IAPP AIGP: AI Transparency That Users Can Understand

AI transparency is useful only when the intended audience can understand what the information means for a real decision. A model card, technical paper, disclosure notice, and user-interface explanation all serve different purposes. Publishing more detail does not automatically make a system more transparent if the people affected cannot tell when AI is involved, what it is doing, what information it uses, or how to challenge an outcome. Home/IAPP/IAPP AIGP: AI Transparency That Users Can UnderstandIAPPPublished October 7, 2026On this pageStart with the audience and the decisionExplain purpose before mechanicsMake…

Read More

IAPP AIGP: AI Governance Roles and Accountability

AI governance fails when responsibility is distributed so widely that nobody can explain who is accountable for a decision. Modern AI systems cross product, engineering, data, security, privacy, legal, procurement, risk, audit, and business operations. Each function owns part of the problem, but the organization still needs clear decision rights for approval, deployment, monitoring, incidents, exceptions, and retirement. Home/IAPP/IAPP AIGP: AI Governance Roles and AccountabilityIAPPPublished October 7, 2026On this pageStart with accountable business ownershipSeparate builders from independent challengeDefine the data accountability chainGive risk acceptance to the right levelMake operational ownership…

Read More

ISC2 CISSP: Software Supply Chain Risk for CISSPs

Modern applications depend on code, packages, build systems, hosted services, signing keys, maintainers, and delivery platforms that may be controlled by different organizations. A vulnerability in a dependency is one risk; a compromised package publisher, stolen build token, tampered artifact, or malicious update is another. Software supply chain security asks whether an organization can establish what it is running, where it came from, which parties were trusted, and how it will respond if any of those assumptions fail. Home/ISC2/ISC2 CISSP: Software Supply Chain Risk for CISSPsISC2Published October 7, 2026On this…

Read More

ISC2 CISSP: Security Models Beyond Memorization

Security models matter when they help engineers and leaders reason about what information is allowed to flow, which subject may act on which object, and what property the system is trying to preserve. Memorizing labels such as Bell-LaPadula or Biba without understanding the problem each model addresses misses their practical value. The models are abstractions that make security assumptions explicit. Home/ISC2/ISC2 CISSP: Security Models Beyond MemorizationISC2Published October 7, 2026On this pageBegin with the property being protectedUse Bell-LaPadula to reason about confidentialityUse Biba to reason about integrityThink about conflict of interest…

Read More

ISC2 CISSP: Security Leadership Across Eight Domains

A security leader rarely gets to choose between security and no security. The real choice is which risks to reduce, which obligations must be met, which controls are proportionate, and what evidence shows the program is working. Those choices span technology, people, vendors, legal responsibilities, and business continuity. Treating security leadership as an inventory of tools hides the accountability that makes the controls useful. Home/ISC2/ISC2 CISSP: Security Leadership Across Eight DomainsISC2Published October 7, 2026On this pageStart with business outcomes and explicit risk ownershipConnect each CISSP domain to a leadership decisionGovern…

Read More

ISC2 CISSP: Privacy Engineering for Security Leaders

Privacy engineering for security leaders turns privacy requirements into technical and operational decisions that can be implemented, tested, and monitored. Privacy and security overlap, but they are not identical. A system can be well protected from attackers and still collect too much data, retain it too long, use it for an unexpected purpose, or make it difficult to honor an individual’s rights. Home/ISC2/ISC2 CISSP: Privacy Engineering for Security LeadersISC2Published October 7, 2026On this pageSeparate privacy from security without separating the teamsMap data before designing controlsMinimize collection and propagationBuild access around…

Read More

ISC2 CISSP: Physical Security in Hybrid Workplaces

Physical security is easy to overlook in cloud-centered workplaces because the most visible controls are identity policies, encryption, and network segmentation. Yet devices can be stolen, confidential conversations overheard, visitors admitted into restricted spaces, and infrastructure damaged by environmental failures. Hybrid work increases the number of places in which people handle sensitive information; it does not eliminate responsibility for physical safeguards. Home/ISC2/ISC2 CISSP: Physical Security in Hybrid WorkplacesISC2Published October 7, 2026On this pageMap assets to places and responsible partiesUse layered controls matched to threat and siteMake visitor and staff access…

Read More

ISC2 CISSP: Cryptographic Key Management at Scale

Encrypting sensitive data does not make it safe if encryption keys can be copied, misused, lost, or silently replaced. In large organizations, keys often cross application teams, cloud services, geographic regions, automation pipelines, backup environments, and outsourced systems. The hardest design problem is therefore not selecting a strong cipher in isolation. It is making every key’s purpose, ownership, access, rotation, recovery, and retirement traceable without disrupting the systems that depend on it. Home/ISC2/ISC2 CISSP: Cryptographic Key Management at ScaleISC2Published October 7, 2026On this pageInventory keys by purpose and impactGenerate and…

Read More

ISC2 CISSP: Business Continuity Without Paper Plans

Business continuity is not proved by possessing a plan. It is proved when an organization can keep essential outcomes available—or restore them within agreed limits—after the assumptions in that plan fail. A cloud outage, unavailable identity provider, ransomware incident, power loss, or critical supplier failure can expose dependencies that looked insignificant on paper. Effective continuity work translates business impact into operational priorities and tests whether real people, systems, facilities, and partners can meet those priorities. Home/ISC2/ISC2 CISSP: Business Continuity Without Paper PlansISC2Published October 7, 2026On this pageBegin with an impact…

Read More

ISACA AAISM: Governing AI Security Risk

Governing AI security risk means deciding which AI-related exposures matter to the enterprise, how much risk the organization is willing to accept, which controls are proportionate, and who has authority to make those decisions. It is broader than securing a model. The risk can come from data, identity, providers, human use, autonomy, business process design, regulatory obligations, or concentration on a small number of external platforms. The topic is the risk-management core of Enterprise AI Governance. In the current AAISM exam outline, AI risk management covers assessment, thresholds, treatment, threats,…

Read More

ISACA AAISM: Controls for Enterprise AI Systems

Controls for enterprise AI systems should protect the entire application path, not only the model endpoint. A production AI service combines identity, data, prompts, retrieval, model providers, tools, memory, APIs, deployment pipelines, monitoring, and human decisions. Each layer can introduce risk, and a safeguard in one layer cannot compensate for every weakness in another. The control model belongs inside Enterprise AI Governance and maps directly to the current AAISM exam emphasis on AI security architecture, lifecycle controls, data management, privacy, trust and safety, monitoring, and risk-based human oversight. The practical…

Read More

ISACA AAISM: AI Model Risk for Security Leaders

An AI model can become a security risk even when it never suffers a conventional software exploit. Sensitive training data may be memorized, a retrieval system may disclose information across tenants, a model or prompt can be manipulated, and an automated action can reach a system it should not control. Security leaders therefore need an AI model risk record that connects technical behavior to business impact. ISACA’s AAISM exam outline covers AI governance, AI risk management and AI technologies and controls; the following method translates those themes into practical review….

Read More

ISACA AAISM: AI Incident Response Governance

AI incident response governance defines how an organization makes accountable decisions when an artificial-intelligence system creates, amplifies, or participates in a security incident. The technical response may involve disabling an endpoint or revoking a credential, but governance determines who can take that action, which evidence must be preserved, when customers or regulators are notified, how business continuity is protected, and what must be proven before the system returns to service. The topic sits naturally inside Enterprise AI Governance. ISACA’s current AAISM exam outline explicitly includes AI-specific incident investigation, documentation, reporting,…

Read More

ISACA CISM: Security Governance That Drives Decisions

Security governance establishes who sets information-protection objectives, who makes risk decisions, how security performance is assessed and what happens when a business unit wants an exception. It is not merely a collection of technical policies. ISACA CISM emphasizes aligning the information security strategy with enterprise goals, legal requirements, organizational culture and stakeholder accountability. ISACA has announced a CISM exam-outline change effective November 3, 2026. On October 25 the current outline still governs earlier sittings, while revised material is being prepared for the forthcoming version. Governance questions in either version require…

Read More