IIBA Certificate in Cybersecurity Analysis IIBA-CCA CCA Exam Questions

Answer : C

Data at rest refers to information that is stored rather than actively moving across networks or being actively processed. This includes data saved on laptops and mobile devices, servers, databases, file shares, removable media, backup tapes, storage arrays, and cloud storage services. Because it sits in storage, the main risks involve unauthorized access (improper permissions, stolen credentials, insider misuse), theft or loss of devices/media, and misconfiguration (publicly exposed storage buckets, overly broad shared drives). Data at rest is also at risk when systems are decommissioned or storage is reused without secure wiping.

Cybersecurity documents emphasize protecting data at rest using layered controls. Encryption at rest ensures stored files or database records remain unreadable without the proper key, reducing impact if storage is stolen or accessed improperly. Strong access control and least privilege limit who can read or modify stored data, while segmentation and secure configuration reduce exposure pathways. Proper key management (separating keys from encrypted data, rotating keys, restricting key access) is critical so encryption meaningfully reduces risk. Additional controls include data classification and handling rules, secure backups (including immutable or protected backups), monitoring and audit logging for sensitive repositories, and secure disposal practices such as cryptographic erase or verified wiping.

Options A and B describe data in transit, not at rest. Option D is incorrect because stored data is not automatically less vulnerable; it is often highly attractive to attackers, so it requires deliberate protection.

Answer : D

Cloud service models are commonly described as stacked layers of responsibility. Software as a Service delivers a complete application to the customer, while the provider manages the underlying platform and infrastructure. Platform as a Service sits one level below SaaS: it provides the managed platform needed to build, deploy, and run applications without the customer having to manage the underlying servers and most core system software.

A defining feature of PaaS is that the provider supplies and manages key platform components such as the operating system, runtime environment, middleware, web/application servers, and often supporting services like managed databases, messaging, scaling, and patching of the platform layer. The customer typically remains responsible for their application code, configuration, identities and access in the application, data classification and protection choices, and secure development practices. This shared responsibility model is central in cybersecurity guidance because it determines which security controls the provider enforces by default and which controls the customer must implement.

Given the answer options, Operating System is the best match because it is a core part of the platform layer that PaaS customers generally do not manage directly. Load balancers and storage can be consumed in multiple models, including IaaS and PaaS, and subscriptions describe a billing approach, not the technical service layer. Therefore, option D correctly reflects what PaaS provides compared to SaaS.

Bottom of Form

Answer : B

KRIs and KPIs are only useful when they are handled as part of a disciplined measurement lifecycle. Cybersecurity governance guidance emphasizes three essential activities: collect, analyze, and report. Organizations must first collect KRI and KPI data consistently from reliable sources such as vulnerability scanners, SIEM logs, IAM systems, ticketing platforms, and asset inventories. Collection requires defined metric owners, clear definitions, standardized time windows, and data quality checks so results are comparable across periods and business units.

Next, organizations analyze the data to understand what it means for risk and performance. Analysis includes trending over time, comparing results to targets and thresholds, correlating indicators to business outcomes, identifying outliers, and determining root causes. For KRIs, analysis highlights rising exposure or control breakdowns such as increasing critical vulnerabilities beyond SLA. For KPIs, analysis evaluates operational effectiveness such as mean time to detect and mean time to remediate.

Finally, organizations report results to the right audiences with the right level of detail. Reporting supports accountability by assigning actions, tracking remediation progress, and escalating when thresholds are exceeded. It also supports decision making by showing where investment, staffing, or control changes will have the greatest risk-reduction and performance impact. The other options are not standard, auditable metric management activities and do not reflect the established lifecycle used in cybersecurity measurement programs.

Answer : C

In a data warehouse, information from multiple operational sources is consolidated, transformed, and related through keys, joins, and business rules. When a Business Analyst defines processes and procedures that describe how data sets interrelate, they are primarily controlling the risk created by data aggregation. Aggregation risk arises when combining multiple datasets produces a new, richer dataset that can change the meaning, sensitivity, or trustworthiness of the information. If relationships and transformation rules are poorly defined or inconsistently applied, the warehouse can generate misleading analytics, incorrect roll-ups, duplicated records, or invalid correlations---directly harming information integrity because decisions are made on inaccurate or improperly combined data.

Well-defined interrelation procedures specify authoritative sources, master data rules, key management, referential integrity expectations, transformation and reconciliation steps, and data lineage. These controls help ensure the warehouse preserves correctness when data is integrated across systems with different formats, definitions, and update cycles. They also support governance by enabling validation checks (for example, balancing totals to source systems, exception handling, and data-quality thresholds) and by making it clear which dataset should be trusted for specific attributes.

Unauthorized access and confidentiality are important warehouse risks, but they are addressed mainly through access controls and encryption. Cross-site scripting is a web application vulnerability and is not the core issue in describing dataset relationships. Therefore, the correct answer is Data Aggregation.

Answer : B

Functional security requirements define what security capabilities a system must provide to protect information and enforce policy. They describe required security functions such as identification and authentication, authorization, role-based access control, privilege management, session handling, auditing/logging, segregation of duties, and account lifecycle processes. Because of this, user privileges are a direct and core concern of functional security requirements: the system must support controlling who can access what, under which conditions, and with what level of permission.

In cybersecurity requirement documentation, ''privileges'' include permission assignment (roles, groups, entitlements), enforcement of least privilege, privileged access restrictions, elevation workflows, administrative boundaries, and the ability to review and revoke permissions. These are functional because they require specific system behaviors and features---for example, the ability to define roles, prevent unauthorized actions, log privileged activities, and enforce timeouts or re-authentication for sensitive operations.

The other options are typically classified differently. System reliability and performance/stability are generally non-functional requirements (quality attributes) describing service levels, resilience, and operational characteristics rather than security functions. Identified vulnerabilities are findings from assessments that drive remediation work and risk treatment; they inform security improvements but are not themselves functional requirements. Therefore, the option best aligned with functional security requirements is user privileges.

Answer : B

A cryptographic hash function supports data in transit primarily by providing integrity assurance. When a sender computes a hash (digest) of a message and the receiver recomputes the hash after receipt, the two digests should match if the message arrived unchanged. If the message is altered in any way while traveling across the network---whether by an attacker, a faulty intermediary device, or transmission errors---the recomputed digest will differ from the original. This difference is the key signal that the message was modified in transit, which is what option B expresses. In practical secure-transport designs, hashes are typically combined with a secret key or digital signature so an attacker cannot simply modify the message and generate a new valid digest. Examples include HMAC for message authentication and digital signatures that hash the content and then sign the hash with a private key. These mechanisms provide integrity and, when keyed or signed, also provide authentication and non-repudiation properties.

Option A is more specifically about authentication of origin, which requires a keyed construction such as HMAC or a signature scheme; a plain hash alone cannot prove who sent the message. Option C is incorrect because keys are not ''converted'' from public to private. Option D relates to confidentiality, which is provided by encryption, not hashing. Therefore, the best answer is B because hashing enables detection of message modification during transit.

Answer : B

Incident management is a structured operational process used to ensure security issues are handled consistently, evidence is preserved, impact is reduced, and improvements are implemented to prevent recurrence. The phases listed in option B match how incident management is commonly documented in operational security programs.

Reporting is the entry point: users, monitoring tools, and service desks raise alerts or tickets, capturing what happened, when, and initial impact. Clear reporting channels and defined severity criteria ensure incidents are escalated quickly and handled by the right teams. Investigation follows, focusing on fact-finding and evidence collection such as logs, endpoint telemetry, network traces, and user statements. Assessment determines scope, business impact, affected assets and data, and the likelihood of continuing compromise. This step drives prioritization and selects the appropriate handling path.

Corrective actions implement containment, eradication, and recovery activities, such as isolating hosts, disabling compromised accounts, applying patches, rotating credentials, restoring from backups, and validating system integrity. Corrective actions also include communications, documentation, and coordination with legal, privacy, and business stakeholders when required. Finally, review is the lessons-learned phase that updates playbooks, improves detections, closes control gaps, and ensures root causes are addressed through durable fixes rather than temporary workarounds.

The other options do not represent standard incident management phases: A is a marketing model, while C and D are incomplete or mis-ordered compared to established incident management lifecycle documentation.