Important IIBA-CCA Exam Questions

Answer: C

Explanation:

Cybersecurity regulations most commonly focus on the protection of personal data, because misuse or exposure can directly harm individuals through identity theft, fraud, discrimination, or loss of privacy. Privacy and data-protection laws typically require organizations to implement appropriate safeguards to protect personal information across its lifecycle, including collection, storage, processing, sharing, and disposal. In cybersecurity governance documentation, this obligation is often expressed through requirements to maintain confidentiality and integrity of personal data, limit access based on business need, and ensure accountability through logging, monitoring, and audits.

Demonstrating protection of personal data generally includes having a documented data classification scheme, clearly defined lawful purposes for processing, retention limits, and secure handling procedures. Technical controls commonly expected include strong authentication, least privilege and role-based access control, encryption for data at rest and in transit, secure key management, endpoint and server hardening, vulnerability management, and continuous monitoring for suspicious activity. Operational capabilities such as incident response, breach detection, and timely notification processes are also emphasized because regulators expect organizations to manage and report material data exposures appropriately.

While protecting applications, intellectual property, and ensuring continuity are important security objectives, they are not the primary focus of many cybersecurity regulations in the same consistent way as personal data protection. Therefore, the best answer is personal data of customers and employees.

Answer: D

Explanation:

Non-repudiation is a security property that provides verifiable evidence of an action or communication so that the parties involved cannot credibly deny their participation later. In web security, it most commonly means being able to prove who sent a message or performed a transaction and, in many cases, that the message was received and recorded. This is why option D is correct: it captures the idea of giving the receiver proof of the sender's identity and giving the sender evidence that the message or transaction was delivered or accepted.

Cybersecurity guidance typically associates non-repudiation with digital signatures, strong identity binding, and protected audit evidence. A digital signature uses asymmetric cryptography so that only the holder of a private key can sign, while anyone with the public key can verify the signature. When combined with trusted certificates, accurate time sources, and protected logs, this creates strong accountability. Non-repudiation also depends on maintaining the integrity of supporting evidence, such as tamper-resistant audit logs, secure log retention, and controlled access to signing keys.

It is different from confidentiality (encryption of traffic), and different from integrity alone (preventing unauthorized modification). It is also different from authorization and auditing, which support accountability but do not, by themselves, provide cryptographic-grade proof that a specific entity performed a specific action. Non-repudiation is especially important for high-trust transactions such as approvals, payments, and legally binding communications.

Answer: A

Explanation:

NIST SP 800-30 Rev. 1 defines qualitative risk severity levels using consistent impact language. In its assessment scale, ''Moderate'' is explicitly tied to events that can be expected to have a serious adverse effect on organizational operations, organizational assets, individuals, other organizations, or the Nation.

A ''serious adverse effect'' is described as outcomes such as a significant degradation in mission capability where the organization can still perform its primary functions but with significantly reduced effectiveness, significant damage to organizational assets, significant financial loss, or significant harm to individuals that does not involve loss of life or life-threatening injuries. This phrasing is used to distinguish ''Moderate'' from ''Low'' (limited adverse effect) and from ''High'' (severe or catastrophic adverse effect).

This classification matters in enterprise risk because it drives prioritization and control selection. A ''Moderate'' rating typically triggers stronger treatment actions than ''Low,'' such as tighter access controls, enhanced monitoring, more frequent vulnerability remediation, stronger configuration management, and improved incident response readiness. It also helps leaders compare risks consistently across systems and business processes by anchoring severity to clear operational and harm-based criteria rather than subjective judgment.

Answer: D

Explanation:

Information classification is the practice of assigning data a sensitivity level so the organization can apply protections that match the business impact if the information is exposed, altered, or becomes unavailable. The core driver for classification is the risk of harm---especially harm caused by unauthorized disclosure. If disclosure would result in regulatory penalties, reputational damage, competitive disadvantage, contractual breach, or harm to customers and employees, the data is classified at a higher level and requires stronger controls. These controls commonly include tighter access restrictions (least privilege and role-based access), stronger authentication, encryption at rest and in transit, stricter handling and sharing rules, audit logging, monitoring, and secure disposal requirements.

While retention can be influenced by compliance obligations, it is not what determines the classification level; retention policies typically reference classification but do not define it. ''Need for access'' is managed through access control decisions, which are applied after the data's sensitivity is understood; classification informs who should have access, not the other way around. ''Timing of availability'' relates to availability requirements and service resilience, which are important, but classification schemes primarily focus on sensitivity and potential damage from inappropriate exposure, with integrity and availability considerations often handled as additional impact dimensions.

Therefore, the best verified basis for information classification is the organization's assessment of risk of loss or harm from disclosure.

Answer: C

Explanation:

Business analysis is responsible for ensuring the solution is correctly understood in terms of business purpose, process flows, data handling, user roles, integrations, and non-functional requirements such as security and privacy. If the solution is not understood well enough, security risks will be missed early, leading to gaps that are expensive and difficult to correct later. This is why option C is the best answer: inadequate understanding prevents reliable identification of threats, sensitive data paths, trust boundaries, and misuse cases during requirements and design stages.

Cybersecurity documents emphasize ''security by design'' and ''shift-left'' practices, meaning risks should be identified and addressed before build and test. Business analysis contributes by eliciting and documenting security requirements, clarifying data classification and retention needs, defining user access and privilege expectations, identifying regulatory and policy constraints, and ensuring interfaces and third-party dependencies are known and assessed. BA also supports threat modeling inputs by providing accurate context about actors, workflows, and data movement, which are essential for identifying where controls like authentication, authorization, logging, encryption, and validation must exist.

Other options align to different roles or stages: budgets are governance and project management constraints, QA limitations are testing risks, and coding-introduced vulnerabilities are primarily addressed through secure coding standards, code review, and developer practices. BA's key cybersecurity risk is incomplete understanding that prevents correct security requirements and risk identification.