IIBA-CCA Exam Preparation Material | Certificate in Cybersecurity Analysis (CCA)

Explanation:
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.

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.

Explanation:
A risk owner is the individual who is accountable for a specific risk being properly managed to an acceptable level. Accountability means the risk owner has the authority and obligation to ensure the risk is assessed, an appropriate treatment decision is made, and the organization follows through― whether that decision is to mitigate, transfer, avoid, or accept the risk. In many governance models, the risk owner is typically a business or technology leader who “owns” the process, asset, or outcome most affected by the risk, and who can commit resources or approve changes needed to address it.
This is different from the person who performs the mitigation work. A risk owner may delegate tasks to control owners, engineers, or project teams, but they remain accountable for ensuring actions are completed, deadlines are met, residual risk is understood, and exceptions are documented and approved according to policy. The risk owner is also the person who should review changes in risk conditions over time, such as new vulnerabilities, changes in threat activity, or business/process changes that alter impact.
Option C describes an implementer or control owner, not necessarily the accountable party.
Option D is simply the discoverer of the risk, and option B is incorrect because risks are often created by circumstances, design choices, or external factors rather than a single person.

Explanation:
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.

Explanation:
Personal information is classified primarily based on the harm that could result from unauthorized disclosure, which maps directly to the confidentiality objective. Cybersecurity and privacy governance frameworks treat personal data as sensitive because exposure can lead to identity theft, fraud, discrimination, personal safety risks, and loss of privacy. Organizations also face regulatory penalties, contractual consequences, and reputational damage when personal data is disclosed without authorization. For this reason, when determining classification, the first and most influential question is typically: “What is the impact if this data becomes known to someone who should not have it?” That impact assessment drives the required protection level and handling rules.
Confidentiality-focused controls then follow from the classification decision, including least privilege and role-based access, strong authentication, encryption at rest and in transit, secure key management, data loss prevention where appropriate, logging and monitoring of access to sensitive records, and strict sharing/transfer procedures.
Integrity and availability matter for personal information, but they are usually secondary in classification decisions. Integrity affects trustworthiness and correctness (for example, incorrect medical or payroll data), and availability affects the ability to access records when needed. However, the defining sensitivity of personal information is that it must not be disclosed improperly. “Accessibility” is not a core security objective used in standard classification models; it is an operational usability concept that is managed through access design after sensitivity is established.