IIBA Certificate in Cybersecurity Analysis IIBA-CCA CCA Exam Questions

Answer : A

Designing an audit log report requires clarity on who is allowed to do what, which actions are considered security-relevant, and what evidence must be captured to demonstrate accountability. Access Control Requirements are the essential business analysis deliverable because they define roles, permissions, segregation of duties, privileged functions, approval workflows, and the conditions under which access is granted or denied. From these requirements, the logging design can specify exactly which events must be recorded, such as authentication attempts, authorization decisions, privilege elevation, administrative changes, access to sensitive records, data exports, configuration changes, and failed access attempts. They also help determine how logs should attribute actions to unique identities, including service accounts and delegated administration, which is critical for auditability and non-repudiation.

Access control requirements also drive necessary log fields and report structure: user or role, timestamp, source, target object, action, outcome, and reason codes for denials or policy exceptions. Without these requirements, an audit log report can become either too sparse to support investigations and compliance, or too noisy to be operationally useful.

A risk log can influence priorities, but it does not define the authoritative set of access events and entitlements that must be auditable. A future state process can provide context, yet it is not as precise as access rules for determining what to log. An internal audit report may highlight gaps, but it is not the primary design input compared to formal access control requirements.

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 : A

Social engineering is the broad technique attackers use when they manipulate human psychology---such as trust, fear, urgency, curiosity, sympathy, authority, or the desire to be helpful---to persuade someone to take an action that benefits the attacker. The key idea in the question is ''exploit human emotions and connection,'' which is the defining characteristic of social engineering. Rather than breaking a system through purely technical means, the attacker targets the person as the easiest path to access, credentials, sensitive information, or physical entry.

Phishing is a specific subtype of social engineering that typically uses email, text messages, or fake websites to trick users into clicking links, opening attachments, or entering credentials. Tailgating is another subtype focused on physical access, where an attacker follows an authorized person into a restricted area by leveraging politeness or social pressure. Malware is malicious software used to compromise systems; it can be delivered through social engineering, but malware itself is not the human-manipulation technique.

Cybersecurity control guidance treats social engineering as a major risk because it can bypass technical protections by causing legitimate users to unintentionally grant access. Common defenses include awareness training, verification procedures (call-back and out-of-band confirmation), least privilege, multi-factor authentication, strong email and web filtering, and clear reporting channels so suspicious requests can be escalated quickly.

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 : 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 : A

When a system processes multiple information types with different security categorizations, cybersecurity standards require the system's overall security categorization to reflect the highest impact level among those information types. This is commonly called the high-water mark approach. The reason is straightforward: the system is only as secure as the protection applied to the most sensitive or most mission-critical data it handles. If the system were categorized at the lowest impact value, an attacker could target the weaker control baseline and still reach higher-impact information, creating an unacceptable gap in confidentiality, integrity, or availability protection.

In practice, categorization evaluates the potential impact of loss for each of the three security objectives and then selects the highest level for each objective across all information types handled by the system. That resulting system categorization then drives control selection, assurance activities, and the rigor of monitoring and incident response expectations. This approach also supports consistent governance: it prevents under-protecting systems that contain a mix of low and high sensitivity information and aligns control strength with worst-case business impact.

Segregating data across systems can be a valid architecture decision to reduce cost or scope, but it is not the required categorization rule; it is an optional design strategy that must be justified and implemented securely. Merging categories or using the lowest value contradicts risk-based protection principles and would likely fail compliance and audit scrutiny.

Answer : C

A security information and event management system (SIEM) is designed to centralize and analyze security-relevant data to support threat detection, compliance reporting, and incident management. SIEM platforms ingest logs and telemetry from many sources such as servers, endpoints, network devices, firewalls, intrusion detection systems, identity providers, cloud services, and business applications. They normalize and correlate these events so analysts can identify suspicious patterns that would be difficult to see in isolated logs, such as repeated failed logins followed by a successful login from an unusual location, privilege escalation, lateral movement indicators, or abnormal data access.

Cybersecurity operational guidance emphasizes SIEM value in three main areas. First, detection and alerting: correlation rules, behavioral analytics, and threat intelligence enrichment help surface high-risk activity. Second, incident response support: SIEM provides timelines, evidence preservation, triage context, and query capabilities that help responders scope and contain incidents. Third, compliance and audit readiness: centralized log retention, integrity controls, and reporting demonstrate that monitoring and control requirements are operating.

The other options do not match the definition. SaaS is a delivery model, not a specific security monitoring capability. A threat risk assessment is a process, not a software product for event collection and correlation. A CASB focuses on governing and protecting cloud application usage, whereas SIEM focuses on cross-environment event aggregation, correlation, and security operations monitoring.