Get IIBA-CCA Exam Practice Questions - Real and Updated

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.

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

Cybersecurity controls are the safeguards an organization implements to reduce risk to an acceptable level. In standard risk-management language, a control is not limited to a one-time review; it is an ongoing capability that is designed, implemented, and operated to prevent, detect, or correct unwanted events. That capability is typically delivered through technology solutions (technical controls) and process solutions (administrative or procedural controls), which is why option B is correct.

Technology controls include items like firewalls, endpoint protection, encryption, multifactor authentication, logging and monitoring, vulnerability scanning, secure configuration baselines, and data-loss prevention. These controls directly enforce security requirements through system behavior and automation, helping reduce the likelihood or impact of threats.

Process controls include policies, standards, access approval workflows, segregation of duties, change management, secure development practices, incident response playbooks, training, and periodic access recertification. These ensure people consistently perform security-critical tasks correctly and create accountability and repeatability.

Options C and D describe possible outcomes or limitations (controls may not fully eliminate risk and may only mitigate part of it), but they are not what controls include. Option A is incorrect because ''only initial reviews'' are insufficient; reviews can be a component of a control, but effective controls require sustained operation, evidence, and reassessment as systems, threats, and business needs change.

Answer : C

In the United States, HIPAA, the Health Insurance Portability and Accountability Act, is the primary federal framework that governs how certain healthcare information must be protected and used. In cybersecurity and compliance documentation, HIPAA is most often discussed through its implementing rules, especially the Privacy Rule and the Security Rule. The Privacy Rule establishes when protected health information may be used or disclosed and grants individuals rights over their health information. The Security Rule focuses specifically on safeguarding electronic protected health information by requiring administrative, physical, and technical safeguards.

From a security controls perspective, HIPAA-driven programs typically include risk analysis and risk management, policies and workforce training, access controls based on least privilege, unique user identification, authentication controls, audit logging, integrity protections, transmission security such as encryption for data in transit, and contingency planning such as backups and disaster recovery. HIPAA also expects organizations to manage third-party risk through appropriate agreements and oversight when vendors handle protected health information.

The other options do not fit the question. The Privacy Act generally applies to U.S. federal agencies' handling of personal records, PIPEDA is a Canadian privacy law, and PCI-DSS is an industry security standard focused on payment card data rather than healthcare data. Therefore, HIPAA is the correct legislation for U.S. healthcare data protection requirements.

Answer : B

Business process diagrams help analysts spot weaknesses in workflows, approvals, handoffs, and segregation of duties, but they do not directly test the technical security of the underlying applications, infrastructure, or configurations. To identify vulnerabilities within solution technology, cybersecurity practice uses penetration testing, which is a controlled, authorized simulation of real-world attacks against systems. A penetration test examines how a solution behaves under adversarial conditions and validates whether security controls actually prevent exploitation, not just whether they are designed on paper.

Penetration testing typically includes reconnaissance, enumeration, and attempts to exploit weaknesses in areas such as authentication, session management, access control, input handling, APIs, encryption usage, misconfigurations, and exposed services. Results provide evidence-based findings, including exploit paths, impact, affected components, and recommended remediations. This makes penetration testing especially valuable before go-live, after major changes, and periodically for high-risk systems to confirm the security posture remains acceptable.

The other options do not fit the objective. A security patch is a remediation action taken after vulnerabilities are known, not a method for discovering them. A smoke test is a basic functional check to confirm the system builds and runs; it is not a security assessment. Vulnerability-as-a-Service is a delivery model that may include scanning or testing, but the recognized tool or technique for identifying vulnerabilities in the technology itself in this context is a penetration test, which directly evaluates exploitability and real security impact.