IIBA-CCA Exam Questions

SSL/TLS relies on digital certificates to support encrypted communications and to help users trust that they are connecting to the correct server. A TLS certificate is typically an X.509 certificate that binds a public key to an identity, such as a domain name, and is digitally signed by a trusted issuer. In most public internet use cases, these certificates are issued by Certificate Authorities that browsers and operating systems already trust through pre-installed root certificates. Because of that trust chain, organizations commonly obtain certificates by purchasing or otherwise obtaining them from certificate authorities, which is why option B is correct.

During the TLS handshake, the server presents its certificate to the client. The client validates the certificate's signature chain, validity period, and that the certificate matches the domain being accessed. Once validated, TLS establishes session keys used to encrypt data in transit and protect it from eavesdropping and tampering. Certificates themselves are not ''similar to unencrypted data,'' and they are not specific to thumb-drive storage; they are used to secure network communications. Certificates also do not primarily provide ''authorization'' to access data. Authorization is typically enforced by application and access control mechanisms after authentication. Certificates support authentication of endpoints and enable secure key exchange, which are prerequisites for secure transport encryption and trustworthy connections.

A risk score is commonly calculated by combining two core factors: how likely a risk scenario is to occur and how severe the consequences would be if it did occur. This is often described in cybersecurity risk documentation as likelihood times impact, or as a structured mapping using a risk matrix. Probability or likelihood reflects the chance that a threat event will exploit a vulnerability under current conditions. It may consider elements such as threat activity, exposure, ease of exploitation, control strength, and historical incident patterns. Impact reflects the magnitude of harm to the organization, usually measured across business disruption, financial loss, legal or regulatory exposure, reputational damage, and harm to confidentiality, integrity, or availability.

While confidentiality, integrity, and availability are essential for understanding what matters and can influence impact ratings, they are typically inputs into impact determination rather than the full scoring method by themselves. Past experience and expert threat assessment can inform likelihood estimates, but they are not the standard calculation model on their own. The key concept is that risk must reflect both chance and consequence; a highly impactful event with very low likelihood may be scored similarly to a moderate impact event with high likelihood depending on the organization's methodology.

Therefore, the most accurate description of how a risk score is calculated is the combination of probability and impact, enabling prioritization and consistent risk treatment decisions.

Recovery Time Objective (RTO) and Recovery Point Objective (RPO) are continuity and resilience targets that define how quickly a system must be restored and how much data loss is acceptable after an interruption. These objectives are derived primarily from system criticality, meaning how essential the system is to business operations, safety, revenue, legal obligations, and customer commitments. Highly critical systems support mission-essential functions or time-sensitive services, so they require shorter RTOs (restore fast) and smaller RPOs (lose little or no data). Less critical systems can tolerate longer outages and larger data gaps, allowing longer RTOs and RPOs.

Cybersecurity and business continuity documents tie RTO/RPO determination to business impact analysis results. The BIA identifies maximum tolerable downtime, operational dependencies, and the consequences of service disruption and data unavailability. From there, organizations set RTO/RPO targets that align with risk appetite and required service levels. Those targets then drive technical and operational controls such as backup frequency, replication methods, high availability architecture, failover design, disaster recovery procedures, monitoring, and routine recovery testing.

Sensitivity focuses on confidentiality needs and may influence encryption and access controls, but it does not directly define acceptable downtime or data loss. Vulnerability describes weakness exposure and is used for threat/risk management, not recovery objectives. Cost is a constraint when selecting recovery solutions, but RTO/RPO are defined by business need and system importance first---then solutions are chosen to meet those targets within budget.

In NIST-style risk assessment, overall likelihood is not a single guess; it is derived by considering two related likelihood components. First is the likelihood that a threat event will be initiated. This reflects how probable it is that a threat actor or source will attempt the attack or that a threat event will occur, considering factors such as adversary capability, intent, targeting, opportunity, and environmental conditions. Second is the likelihood that an initiated event will succeed, meaning the attempt results in the adverse outcome. This depends heavily on the organization's existing protections and conditions, including control strength, system exposure, vulnerabilities, misconfigurations, detection and response capability, and user behavior.

Option A matches this structure: analysts evaluate both attack initiation likelihood and initiated attack success likelihood to reach an overall view of likelihood. A high initiation likelihood with low success likelihood might occur when an organization is frequently targeted but has strong defenses. Conversely, low initiation likelihood with high success likelihood might apply to niche systems that are rarely targeted but poorly protected.

The other options are incomplete or misplaced. Risk impact is a separate dimension from likelihood, and mitigation strategy is an output of risk treatment, not an input to likelihood. Site traffic and commerce volume can influence exposure but do not define likelihood by themselves. Past experience and trends are useful evidence, but they support estimating the two likelihood components rather than replacing them.

Business analysts support cybersecurity compliance primarily by ensuring that security and privacy expectations are translated into clear, testable requirements that are built into the solution. This includes eliciting applicable organizational security policies, standards, and control objectives, then mapping them into functional and non-functional requirements such as authentication methods, role-based access, logging and audit trail needs, encryption requirements, session controls, data retention, and segregation of duties. When security policies are reflected in the solution requirements, they become part of the delivery lifecycle: they can be designed, implemented, validated in testing, and verified during acceptance. This creates traceability from policy to requirement to control implementation, which is essential for audits and for demonstrating due diligence.

Option A is typically the responsibility of governance, risk, and compliance functions or internal audit, not the BA. Option C is usually performed by security testing specialists, QA teams, or application security engineers using techniques like SAST, DAST, and penetration testing. Option D is largely an operational management and compliance enforcement function, supported by training, monitoring, and disciplinary processes. The BA's distinct contribution is ensuring policy-driven security controls are captured in requirements and embedded into the solution design and delivery artifacts.