[Apr-2026] IIBA IIBA-CCA Exam: Basic Questions With Answers
New 2026 Realistic Free IIBA IIBA-CCA Exam Dump Questions and Answer
NEW QUESTION # 15
The main phases of incident management are:
- A. initiation, planning, action, closing.
- B. assess, investigate, report, respond, legal compliance.
- C. reporting, investigation, assessment, corrective actions, review.
- D. awareness, interest, desire, action.
Answer: C
Explanation:
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.
NEW QUESTION # 16
ITIL Information Technology Infrastructure Library defines:
- A. a set of security requirements that every business technology system must meet.
- B. a standard of best practices for IT Service Management.
- C. how technology and hardware systems interface securely with one another.
- D. the standard set of components used in every business technology system.
Answer: B
Explanation:
ITIL is a widely adopted framework that defines best-practice guidance for IT Service Management. Its focus is on how organizations design, deliver, operate, and continually improve IT services so they reliably support business outcomes. In cybersecurity and service delivery documentation, ITIL is often referenced because strong service management processes are foundational to secure operations. For example, ITIL practices such as incident management, problem management, change enablement, configuration management, and service continuity help ensure security controls are implemented consistently and that deviations are identified, tracked, and corrected.
ITIL does not define how hardware systems interface securely with one another; that is more aligned with architecture standards, security engineering, and network or platform design frameworks. It also does not prescribe a universal set of components for every technology system; that belongs to reference architectures and enterprise architecture standards. Likewise, ITIL is not primarily a security requirements standard. While ITIL supports security governance through practices like risk management, access management, and information security management integration, it does not itself serve as a mandatory security control catalog.
From a cybersecurity perspective, ITIL contributes by promoting repeatable processes, clear roles and responsibilities, measurable service levels, and continual improvement. These elements reduce operational risk, improve response effectiveness, and strengthen accountability-key requirements for maintaining confidentiality, integrity, and availability in production environments.
NEW QUESTION # 17
Which organizational area would drive a cybersecurity infrastructure Business Case?
- A. Legal
- B. Risk
- C. Finance
- D. IT
Answer: B
Explanation:
A cybersecurity infrastructure business case is typically driven by the Risk function because the justification for security investments is grounded in reducing enterprise risk to an acceptable level and aligning with the organization's risk appetite and regulatory obligations. Risk-focused teams (often working with the CISO and security governance) translate threats, vulnerabilities, and control gaps into business impact terms such as likelihood of adverse events, potential operational disruption, financial exposure, regulatory penalties, and reputational harm. This framing is what a formal business case requires: a clear problem statement, quantified or prioritized risk scenarios, expected risk reduction from proposed controls, and how residual risk compares to tolerance thresholds.
While IT usually leads implementation and provides architecture, sizing, and operational cost estimates, IT alone does not typically "drive" the business case without the risk rationale that explains why the investment is necessary and what enterprise outcomes it protects. Legal contributes requirements related to compliance, contracts, and breach handling, but it generally supports rather than owns investment prioritization. Finance evaluates budgeting, funding options, and return-on-investment assumptions, yet it relies on risk inputs to understand why the spend is warranted and what loss exposure is being reduced.
Therefore, the organizational area most responsible for driving a cybersecurity infrastructure business case-by defining the risk problem, articulating risk-based benefits, and enabling executive decision-making-is Risk.
Bottom of Form
NEW QUESTION # 18
NIST 800-30 defines cyber risk as a function of the likelihood of a given threat-source exercising a potential vulnerability, and:
- A. the effectiveness of the control assurance framework.
- B. the probability of detecting damage to the infrastructure.
- C. the pre-disposing conditions of the vulnerability.
- D. the resulting impact of that adverse event on the organization.
Answer: D
Explanation:
NIST SP 800-30 describes risk using a classic risk model: risk is a function of likelihood and impact. In this model, a threat-source may exploit a vulnerability, producing a threat event that results in adverse consequences. The likelihood component reflects how probable it is that a threat event will occur and successfully cause harm, considering factors such as threat capability and intent (or in non-adversarial cases, the frequency of hazards), the existence and severity of vulnerabilities, exposure, and the strength of current safeguards. However, likelihood alone does not define risk; a highly likely event that causes minimal harm may be less important than a less likely event that causes severe harm.
The second required component is the impact-the magnitude of harm to the organization if the adverse event occurs. Impact is commonly evaluated across mission and business outcomes, including financial loss, operational disruption, legal or regulatory consequences, reputational damage, and loss of confidentiality, integrity, or availability. This is why option D is correct: NIST's definition explicitly ties the risk expression to the resulting impact on the organization.
The other options may influence likelihood assessment or control selection, but they are not the missing definitional element. Detection probability and control assurance relate to monitoring and governance; predisposing conditions can shape likelihood. None replace the
NEW QUESTION # 19
Violations of the EU's General Data Protection Regulations GDPR can result in:
- A. a complete audit of the enterprise's security processes.
- B. fines of €20 million or 4% of annual turnover, whichever is greater.
- C. fines of €20 million or 4% of annual turnover, whichever is less.
- D. mandatory upgrades of the security infrastructure.
Answer: B
Explanation:
The GDPR establishes a regulatory penalty framework intended to make privacy and data-protection obligations enforceable across organizations of any size. Under GDPR, the most severe administrative fines can reach up to €20 million or up to 4% of the organization's total worldwide annual turnover of the preceding financial year, whichever is higher. That "whichever is greater" clause is critical: it prevents large enterprises from treating privacy violations as a minor cost of doing business and ensures the sanction can scale with the organization's economic size and risk impact.
Cybersecurity governance and risk documents typically emphasize GDPR as a driver for enterprise risk management because the consequences extend beyond monetary fines. A confirmed violation often triggers regulatory investigations, mandatory corrective actions, and potential restrictions on processing activities. Organizations may also face indirect impacts such as breach notification costs, legal claims from affected individuals, reputational harm, loss of customer trust, and increased oversight by regulators and auditors.
From a controls perspective, GDPR penalties reinforce the need for strong security and privacy-by-design practices: data minimization, lawful processing, documented purposes, retention controls, encryption where appropriate, access control and least privilege, monitoring and incident response readiness, and evidence-based accountability through policies, records, and audit trails. Selecting option C correctly reflects GDPR's maximum fine structure and its risk-based deterrence model.
NEW QUESTION # 20
Certificates that provide SSL/TLS encryption capability:
- A. can be purchased from certificate authorities.
- B. can provide authorization of data access.
- C. are similar to the unencrypted data.
- D. are for data located on thumb drives.
Answer: A
Explanation:
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.
NEW QUESTION # 21
Which organizational resource category is known as "the first and last line of defense" from an attack?
- A. Classified Data
- B. Endpoint Devices
- C. Firewalls
- D. Employees
Answer: D
Explanation:
In cybersecurity guidance, employees are often described as the first and last line of defense because human actions influence nearly every stage of an attack. They are the first line since many threats begin with user interaction: phishing emails, malicious links, social engineering calls, unsafe file handling, weak passwords, and accidental disclosure of sensitive information. A well-trained user who recognizes suspicious requests, verifies identities, and reports anomalies can stop an incident before any technical control is even engaged.
Employees are also the last line because technical protections such as firewalls, filters, and endpoint tools are not perfect. Attackers routinely bypass or evade automated defenses using stolen credentials, living-off-the-land techniques, misconfigurations, or novel malware. When those controls fail, the organization still depends on people to apply secure behaviors: following least privilege, protecting credentials, using multifactor authentication correctly, confirming out-of-band requests for payments or data, and escalating unusual activity quickly. Incident response, containment, and recovery also depend on humans making correct decisions under pressure, following documented procedures, and communicating accurately.
Cybersecurity documents emphasize that a strong security culture, regular awareness training, role-based education, clear reporting channels, and consistent policy enforcement reduce human-enabled risk and turn employees into an effective security control rather than a vulnerability.
NEW QUESTION # 22
What operational practice would risk managers employ to demonstrate the effectiveness of security controls?
- A. Security Awareness Training
- B. Change Management
- C. Penetration Testing
- D. Metrics Reporting
Answer: D
Explanation:
Risk managers demonstrate the effectiveness of security controls by using metrics reporting because metrics provide objective, repeatable evidence that controls are operating as intended and are producing measurable outcomes. In cybersecurity governance, "control effectiveness" is shown through performance indicators and trend data, not just by stating that a control exists. Metrics translate technical activity into risk-relevant results that leadership can understand and act on.
Common control-effectiveness metrics include patch compliance rates and time-to-remediate critical vulnerabilities, percentage of systems meeting secure configuration baselines, multifactor authentication coverage, privileged access review completion rates, mean time to detect and respond, incident volume and severity trends, phishing simulation outcomes, and the percentage of logs successfully collected and retained for monitoring. Risk managers also use key risk indicators to track whether residual risk is increasing or decreasing, and they compare results against defined thresholds and risk appetite.
While penetration testing can validate exposure and reveal weaknesses, it is periodic and scenario-based; it does not continuously demonstrate ongoing control performance across the environment. Change management is essential for stability and risk reduction, but it is a process control rather than a reporting practice used to demonstrate effectiveness. Security awareness training improves user behavior, yet effectiveness still needs measurement through metrics such as completion rates and simulated phishing results. Therefore, metrics reporting is the operational practice most directly used to demonstrate control effectiveness.
NEW QUESTION # 23
What term is defined as a fix to software programming errors and vulnerabilities?
- A. Control
- B. Patch
- C. Log
- D. Release
Answer: B
Explanation:
A patch is a vendor- or developer-provided update intended to correct defects in software, including programming errors and security vulnerabilities. Cybersecurity and IT operations documents describe patching as a primary method of vulnerability remediation because many attacks succeed by exploiting known weaknesses for which fixes already exist. When a vulnerability is disclosed, the vendor may publish a patch that changes code, updates components, adjusts configuration defaults, or replaces vulnerable libraries. Applying the patch reduces the likelihood that an attacker can use that weakness to gain unauthorized access, execute malicious code, elevate privileges, or disrupt availability.
A patch is different from a control, which is a broader safeguard (technical, administrative, or physical) used to reduce risk; patching itself can be part of a control, such as a patch management program. It is also different from a release, which is a broader software distribution that may include new features, improvements, and multiple fixes; a patch is usually more targeted and may be issued between major releases. A log is an audit record of events and is used for monitoring, troubleshooting, and incident investigation-not for fixing code defects.
Cybersecurity guidance emphasizes disciplined patch management: maintaining asset inventories, prioritizing patches by risk and exposure, testing changes, deploying promptly, verifying installation, and documenting exceptions to manage residual risk.
NEW QUESTION # 24
What is whitelisting in the context of network security?
- A. Grouping assets together based on common security requirements, and placing each group into an isolated network zone
- B. Explicitly allowing identified people, groups, or services access to a particular privilege, service, or recognition
- C. Running software to identify any malware present on a computer system
- D. Denying access to applications that have been determined to be malicious
Answer: B
Explanation:
Whitelisting, often called an "allow list," is a security approach where access is granted only to explicitly approved identities, services, applications, IP addresses, domains, or network flows. In network security, this means the default stance is "deny by default," and only pre-authorized entities are allowed to communicate or use specific resources. Option C matches this definition because it describes the core idea: explicitly permitting known, approved subjects (people, groups, service accounts, systems) to access a defined privilege or service.
Cybersecurity documents emphasize whitelisting as a strong risk-reduction technique because it constrains the attack surface. Instead of trying to block every bad thing (which is difficult due to evolving threats), whitelisting focuses on allowing only what is required for business operations. Examples include firewall rules that only permit specific source IPs to reach an admin interface, network segmentation policies that allow only required ports between zones, and application whitelisting that permits only approved executables to run. When implemented correctly, it reduces lateral movement opportunities, limits command-and-control traffic, and prevents unauthorized tools from executing.
Whitelisting is different from segmentation (option A), which is about isolating zones based on security needs, and different from blacklisting (option B), which blocks known-bad items. It is also not malware scanning (option D), which detects malicious code after it appears. Whitelisting aligns with least privilege and zero trust principles by tightly controlling what is allowed.
NEW QUESTION # 25
The process by which organizations assess the data they hold and the level of protection it should be given based on its risk to loss or harm from disclosure, is known as:
- A. vulnerability assessment.
- B. information categorization.
- C. information classification.
- D. internal audit.
Answer: C
Explanation:
Information classification is the formal process of evaluating the data an organization creates or holds and assigning it a sensitivity level so the organization can apply the right safeguards. Cybersecurity policies describe classification as the foundation for consistent protection because it links the potential harm from unauthorized disclosure, alteration, or loss to specific handling and control requirements. Typical classification labels include Public, Internal, Confidential, and Restricted, though names vary by organization. Once data is classified, required protections can be specified, such as encryption at rest and in transit, access restrictions based on least privilege, approved storage locations, monitoring requirements, retention periods, and secure disposal methods.
This is not a vulnerability assessment, which focuses on identifying weaknesses in systems, applications, or configurations. It is also not an internal audit, which evaluates whether controls and processes are being followed and are effective. Option D, information categorization, is often used in some frameworks to describe assigning impact levels (for example, confidentiality, integrity, availability impact) to information types or systems, mainly to drive control baselines. While related, the question specifically emphasizes assessing data and deciding the level of protection based on risk from disclosure, which aligns most directly with classification programs used to govern labeling and handling rules across the organization.
A strong classification program improves security consistency, supports compliance, reduces accidental exposure, and helps prioritize controls for the most sensitive information assets.
NEW QUESTION # 26
What stage of incident management would "strengthen the security from lessons learned" fall into?
- A. Recovery
- B. Response
- C. Remediation
- D. Detection
Answer: C
Explanation:
"Strengthen the security from lessons learned" fits the remediation stage because it focuses on eliminating root causes and improving controls so the same incident is less likely to recur. In incident management lifecycles, response is about immediate actions to contain and manage the incident (triage, containment, eradication actions in progress, communications, and preserving evidence). Detection is the identification and confirmation stage (alerts, analysis, validation, and initial classification). Recovery is restoring services to normal operation and verifying stability, including bringing systems back online, validating data integrity, and meeting recovery objectives.
After the environment is stable, organizations conduct a post-incident review and then implement corrective and preventive actions. That work is remediation: closing exploited vulnerabilities, hardening configurations, rotating credentials and keys, tightening access and privileged account controls, improving monitoring and logging coverage, updating firewall rules or segmentation, refining secure development practices, and correcting process gaps such as weak change management or incomplete asset inventory. Remediation also includes updating policies and playbooks, enhancing detection rules based on observed attacker techniques, and training targeted groups if human factors contributed.
Cybersecurity guidance emphasizes documenting lessons learned, assigning owners and deadlines, validating fixes, and tracking completion because "lessons learned" without implemented change does not reduce risk. The defining characteristic is durable improvement to the control environment, which is why this activity belongs to remediation rather than response, detection, or recovery.
NEW QUESTION # 27
Which of the following control methods is used to protect integrity?
- A. Biometric Verification
- B. Backups and Redundancy
- C. Principle of Least Privilege
- D. Anti-Malicious Code Detection
Answer: C
Explanation:
Integrity means information and systems remain accurate, complete, and protected from unauthorized or improper modification. The Principle of Least Privilege is a direct integrity protection control because it limits who can change data and what changes they are allowed to make. Under least privilege, users, applications, and service accounts receive only the minimum permissions needed to perform approved tasks, and nothing more. This reduces the chance that an attacker using a compromised account can alter records, manipulate transactions, or change configurations, and it also reduces accidental changes by well-meaning users who do not need write or administrative rights.
Least privilege is commonly enforced through role-based access control, separation of duties, restricted administrative roles, just-in-time elevation for privileged tasks, and periodic access reviews to remove excess permissions. These practices are emphasized in cybersecurity frameworks because integrity failures often occur when excessive access allows unauthorized edits to sensitive data, logs, security settings, or application code.
The other options relate to security but are less directly tied to integrity as the primary objective. Biometric verification is an authentication method that helps confirm identity; it supports access control broadly, but it does not by itself limit modification capability once access is granted. Anti-malicious code detection helps prevent malware that could corrupt data, but it is primarily a detection/prevention tool rather than the foundational control for authorized modification. Backups and redundancy primarily support availability and recovery after corruption, not the prevention of unauthorized changes.
NEW QUESTION # 28
Public & Private key pairs are an example of what technology?
- A. Virtual Private Network
- B. IoT
- C. Network Segregation
- D. Encryption
Answer: D
Explanation:
Public and private key pairs are the foundation of asymmetric encryption, also called public key cryptography. In this model, each entity has two mathematically related keys: a public key that can be shared widely and a private key that must be kept secret. The keys are designed so that what one key does, only the other key can undo. This enables two core security functions used throughout cybersecurity architectures.
First, confidentiality: data encrypted with a recipient's public key can only be decrypted with the recipient's private key. This allows secure communication without having to share a secret key in advance, which is especially important on untrusted networks like the internet. Second, digital signatures: a sender can sign data with their private key, and anyone can verify the signature using the sender's public key. This provides authenticity (proof the sender possessed the private key), integrity (the data was not altered), and supports non-repudiation when combined with proper key custody and audit practices.
These mechanisms underpin widely used security controls such as TLS for secure web connections, secure email standards, code signing, and certificate-based authentication. A VPN may use public key cryptography during key exchange, but the key pair itself is specifically an encryption technology. IoT and network segregation are unrelated categories.
NEW QUESTION # 29
What risk to information integrity is a Business Analyst aiming to minimize, by defining processes and procedures that describe interrelations between data sets in a data warehouse implementation?
- A. Data Aggregation
- B. Cross-Site Scripting
- C. Unauthorized Access
- D. Confidentiality
Answer: A
Explanation:
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.
NEW QUESTION # 30
Which scenario is an example of the principle of least privilege being followed?
- A. A manager who is conducting performance appraisals is granted access to HR files for all employees
- B. Certain users are granted administrative access to their network account, in case they need to install a web-app
- C. An application administrator has full permissions to only the applications they support
- D. All application and database administrators have full permissions to every application in the company
Answer: C
Explanation:
The principle of least privilege requires that users, administrators, services, and applications are granted only the minimum access necessary to perform authorized job functions, and nothing more. Option A follows this principle because the administrator's elevated permissions are limited in scope to the specific applications they are responsible for supporting. This reduces the attack surface and limits blast radius: if that administrator account is compromised, the attacker's reach is constrained to only those applications rather than the entire enterprise environment.
Least privilege is typically implemented through role-based access control, separation of duties, and privileged access management practices. These controls ensure privileges are assigned based on defined roles, reviewed regularly, and removed when no longer required. They also promote using standard user accounts for routine tasks and reserving administrative actions for controlled, auditable sessions. In addition, least privilege supports stronger accountability through logging and change tracking, because fewer people have the ability to make high-impact changes across systems.
The other scenarios violate least privilege. Option B grants excessive enterprise-wide permissions, creating unnecessary risk and enabling widespread damage from mistakes or compromise. Option C provides "just in case" administrative access, which cybersecurity guidance explicitly discourages because it increases exposure without a validated business need. Option D is overly broad because access to all HR files exceeds what is required for performance appraisals, which typically should be limited to relevant employee records only.
NEW QUESTION # 31
Analyst B has discovered multiple sources which can harm the organization's systems. What has she discovered?
- A. Ransomware
- B. Hacker
- C. Threat
- D. Breach
Answer: C
Explanation:
Multiple sources that can harm an organization's systems are classified as threats. In cybersecurity risk terminology, a threat is any circumstance, event, actor, or condition with the potential to adversely impact confidentiality, integrity, or availability. Threats can be human (external attackers, insiders, third-party compromises), technical (malware, ransomware campaigns, exploit kits), operational (misconfigurations, weak processes, inadequate monitoring), or environmental (power disruption, natural disasters). This differs from a breach, which is the realized outcome where unauthorized access or disclosure has already occurred. It also differs from hacker, which refers to one type of threat actor rather than the broader category of potential harm. Ransomware is a specific threat type (malware that encrypts data and demands payment), not a general term for multiple sources of harm. Cybersecurity documents commonly pair "threats" with "vulnerabilities" and "controls": threats exploit vulnerabilities to create risk; controls reduce either the likelihood of exploitation or the impact if exploitation occurs. Identifying "multiple sources which can harm systems" is essentially threat identification-an early and ongoing step in risk management used to inform security architecture, monitoring, and incident preparedness. Therefore, the correct concept is threat.
NEW QUESTION # 32
Information classification of data is a level of protection that is based on an organization's:
- A. timing of availability for automated systems.
- B. need for access by employees.
- C. risk to loss or harm from disclosure.
- D. retention for auditing purposes.
Answer: C
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.
NEW QUESTION # 33
How should categorization information be used in business impact analysis?
- A. To assess whether information should be shared with other systems
- B. To ensure that systems are designed to support the appropriate security categorization
- C. To determine the time and effort required for business impact assessment
- D. To identify discrepancies between the security categorization and the expected business impact
Answer: D
NEW QUESTION # 34
SSL/TLS encryption capability is provided by:
- A. protocols.
- B. passwords.
- C. certificates.
- D. controls.
Answer: A
Explanation:
SSL and its successor TLS are cryptographic protocols designed to provide secure communications over untrusted networks. The encryption capability comes from the TLS protocol suite, which defines how two endpoints negotiate security settings, authenticate, exchange keys, and protect data as it travels between them. During the TLS handshake, the endpoints agree on a cipher suite, establish shared session keys using secure key exchange methods, and then use symmetric encryption and integrity checks to protect application data against eavesdropping and tampering. Because TLS specifies these mechanisms and the sequence of steps, it is accurate to say that encryption capability is provided by protocols.
Certificates are important but they are not the encryption mechanism itself. Digital certificates primarily support authentication and trust by binding a public key to an identity and enabling verification through a trusted certificate authority chain. Certificates help prevent impersonation and man-in-the-middle attacks by allowing clients to validate the server's identity, and in mutual TLS they can validate both parties. However, certificates alone do not define how encryption is negotiated or applied; TLS does.
Passwords are unrelated to transport encryption; they are an authentication secret and do not provide session encryption for network traffic. "Controls" is too general: SSL/TLS is indeed a security control, but the question asks specifically what provides the encryption capability. That capability is implemented and standardized by the SSL/TLS protocols, which orchestrate key establishment and encrypted communication.
NEW QUESTION # 35
Other than the Requirements Analysis document, in what project deliverable should Vendor Security Requirements be included?
- A. Business Continuity Plan
- B. Request For Proposals
- C. Project Charter
- D. Training Plan
Answer: B
Explanation:
Security requirements in an RFP typically cover topics such as secure development practices, vulnerability management, patching and support timelines, encryption for data at rest and in transit, identity and access controls, audit logging, incident notification timelines, subcontractor controls, data residency and retention, penetration testing evidence, compliance attestations, and right-to-audit provisions. The RFP also enables objective scoring by requesting documented evidence such as security certifications, control descriptions, and responses to standardized security questionnaires.
A training plan and business continuity plan are operational deliverables and do not drive vendor selection criteria. A project charter sets scope and governance at a high level, but it is not the primary procurement artifact for binding vendor security obligations. Therefore, the correct answer is Request For Proposals.
NEW QUESTION # 36
How should categorization information be used in business impact analysis?
- A. To assess whether information should be shared with other systems
- B. To ensure that systems are designed to support the appropriate security categorization
- C. To determine the time and effort required for business impact assessment
- D. To identify discrepancies between the security categorization and the expected business impact
Answer: D
Explanation:
Security categorization (commonly based on confidentiality, integrity, and availability impact levels) is meant to reflect the level of harm that would occur if an information type or system is compromised. A business impact analysis, on the other hand, examines the operational and organizational consequences of disruptions or failures-such as loss of revenue, inability to deliver critical services, legal or regulatory exposure, reputational harm, and impacts to customers or individuals. Because these two activities look at impact from different but related perspectives, categorization information should be used during the BIA to confirm that the stated security categorization truly matches real business consequences.
Using categorization as an input helps analysts validate assumptions about criticality, sensitivity, and tolerance for downtime. If the BIA shows that outages or data compromise would produce greater harm than the existing categorization implies, that discrepancy signals under-classification and insufficient controls. Conversely, if the BIA demonstrates limited impact, it may indicate over-classification, potentially driving unnecessary cost and operational burden. Identifying these mismatches early supports better risk decisions, prioritization of recovery objectives, and selection of controls proportionate to actual impact.
The other options describe activities that may occur in architecture, governance, or project planning, but they are not the primary purpose of using categorization information in a BIA. The key value is reconciliation: aligning security impact levels with verified business impact.
NEW QUESTION # 37
......
IIBA IIBA-CCA Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
Guaranteed Success in Cybersecurity Analysis IIBA-CCA Exam Dumps: https://www.itexamdownload.com/IIBA-CCA-valid-questions.html
IIBA-CCA Practice Test Engine: Try These 77 Exam Questions: https://drive.google.com/open?id=1bUJeDqSzqGwCFMvVaR-lixddyG5jEdkD