CISA Exam Dumps - Isaca Certification Questions and Answers

 The best strategy to optimize data storage without compromising data retention practices is to limit the size of file attachments being sent via email. This strategy can reduce the amount of storage space required for email messages, as well as the network bandwidth consumed by email traffic. File attachments can be large and often contain redundant or unnecessary information that can be compressed, converted, or removed before sending. By limiting the size of file attachments, the sender can encourage the use of more efficient formats, such as PDF or ZIP, or alternative methods of sharing files, such as cloud storage or web links. This can also improve the security and privacy of email communications, as large attachments may pose a higher risk of being intercepted, corrupted, or infected by malware.

A Web Application Firewall (WAF) (A) is the best control to mitigate SQL injection attacks because it can detect and block malicious SQL queries before they reach the application. WAFs analyze incoming requests, filter SQL injection attempts, and provide an additional layer of security for web applications.

Other options:

SQL server hardening (B) improves security but does not specifically address SQL injection.

Patch management (C) is necessary but does not provide immediate protection against new SQL injection attacks.

Physical controls (D) are unrelated to application-layer threats like SQL injection.

The best criteria for monitoring an IT vendor’s service levels are the performance metrics, as they provide quantifiable and measurable indicators of how well the vendor is delivering the agreed-upon services, such as availability, reliability, quality, timeliness, and customer satisfaction. A service auditor’s report is a document that provides an independent opinion on the vendor’s controls and processes, but it may not reflect the actual service levels or performance. A surprise visit to the vendor may help to verify the vendor’s compliance and operations, but it may not be feasible or effective for monitoring the service levels on a regular basis. An interview with the vendor may help to obtain feedback and insights from the vendor’s perspective, but it may not be objective or reliable formonitoring the service levels. References: CISA Review Manual(Digital Version), Chapter 2: Governanceand Management of IT, Section 2.4: IT Service Delivery and Support

Enterprise Architecture (EA) governance requires proper oversight and separation of duties to ensure strategic alignment and risk management.

Option A (Correct):If IT application owners have sole authority over architecture approval, there is a high risk of inadequate governance, lack of strategic alignment, and potential conflicts of interest. Architecture decisions should involve multiple stakeholders, including business and security teams, to ensure compliance, security, and business alignment.

Option B (Incorrect):While having the CIO chair the architecture review board might not be ideal, it is not thegreatestconcern. The CIO is a senior leader who can provide oversight and direction, even if additional governance mechanisms should be in place.

Option C (Incorrect):Reviewing security requirements within the EA program is abest practice, as it ensures that security is embedded into enterprise architecture rather than treated as an afterthought.

Option D (Incorrect):Enterprise architecture should ideally encompass both IT and business processes. Governing non-IT-related projects is not inherently problematic, as EA is designed to align business strategy with IT infrastructure.

The observation that should be of most concern to the auditor when reviewing security controls related to collaboration tools for a business unit responsible for intellectual property and patents is that employees can share files with users outside the company through collaboration tools. Collaboration tools are software or hardware devices that enable users to communicate, cooperate, and coordinate with each other on a common task or project. Collaboration tools can facilitate information sharing and knowledge exchange among users, but they can also pose security risks if not properly controlled or managed. Employees can share files with users outside the company through collaboration tools, as this can compromise the security and confidentiality of intellectual property and patents, which are valuable and sensitive assets of the organization. Employees may share files with unauthorized or untrusted users who may misuse or disclose the intellectual property and patents, either intentionally or unintentionally. This can cause harm or damage to the organization, such as loss of competitive advantage, reputation, revenue, or legal rights. Training was not provided to the department that handles intellectual property and patents is a possible observation that could indicate a security issue related to collaboration tools for a business unit responsible for intellectual property and patents, but it is not the most concerning one. Training is anactivity that educates and instructs users on how to use collaboration tools effectively and securely, such as how to access, share, store, and protect information using collaboration tools. Training was not provided to the department that handles intellectual property and patents, as this can affect the awareness and competence of users on collaboration tools, and increase the likelihood of errors or mistakes that may compromise the security or quality of information. However, this observation may not be directly related to collaboration tools, as it may apply to any information system or resource used by the department. Logging and monitoring for content filtering is not enabled is a possible observation that could indicate a security issue related to collaboration tools for a business unit responsible for intellectual property and patents, but it is not the most concerning one. Logging and monitoring are processes that record and analyze the events or activities that occur on an information system or network, such as user actions, system operations, data changes, errors, alerts, etc. Content filtering is a technique that blocks or allows access to certain types of information based on predefined criteria or rules, such as keywords, categories, sources, etc. Logging and monitoring for content filtering is not enabled, as this can affect the auditability, accountability, and visibility of collaboration tools, and prevent detection or investigation of security incidents or violations related to information sharing using collaboration tools. However, this observation may not be specific to collaboration tools, as it may affect any information system or network that uses content filtering. The collaboration tool is hosted and can only be accessed via an Internet browser is a possible observation that could indicate a security issue related to collaboration tools for a business unit responsible for intellectual property and patents, but it is not the most concerning one. A hosted collaboration tool is a type of cloud-based service that provides collaboration functionality over the Internet without requiring installation or maintenance on local devices. An Internet browser is a software application that enables users to access and interact with web-based content or services. The collaboration tool is hosted and can only be accessed via an Internet browser, as this can affect the availability and reliability of collaboration tools, and introduce security or privacy risks for information sharing using collaboration tools. However, this observation may not be unique to collaboration tools, as it may apply to any cloud-based service that uses an Internet browser. 

A BCP must stay current with organizational changes to ensure its effectiveness during a disruption. Personnel changes and environmental updates are directly relevant to how the BCP would be executed.

References

ISACA CISA Review Manual (Current Edition) - Chapter on Business Continuity and Disaster Recovery

Industry Standards (e.g., ISO 22301, NIST SP 800-34) - Guidelines for maintaining and updating a Business Continuity Plan

The best indicator of whether a PIR performed by the PMO was effective is whether project outcomes have been realized. Project outcomes are the benefits or value that a project delivers to its stakeholders, such as improved efficiency, quality, customer satisfaction, or revenue. A PIR should evaluate whether project outcomes have been achieved in accordance with project objectives, scope, budget, and schedule. The other options are not as good as project outcomes in determining the effectiveness of a PIR. Lessons learned are valuable inputs for improving future projects, but they do not measure whether project outcomes have been realized. Management approval of the PIR report is a sign of acceptance and support for the PIR findings and recommendations, but it does not reflect whether project outcomes have been achieved. The review performed by an external provider is a way of ensuring objectivity and independence for the PIR, but it does not guarantee whether project outcomes have been realized. References: CISA Review Manual (Digital Version), Chapter 3, Section 3.3

This directly addresses the gap for new hires, creates a consistent expectation regardless of hiring date, and formalizes the process within organizational policy.

References

ISACA CISA Review Manual (Current Edition) - Chapters on Information Security Policies, Training and Awareness

Industry Best Practices for Security Awareness - Emphasize the importance of timely and comprehensive training for new employees.

 The most important factor to consider when developing a service level agreement (SLA) is the description of the services from the viewpoint of the client organization, because the SLA shouldreflect the needs and expectations of the client and specify the measurable outcomes and performance indicators that the provider must deliver34. The description of the services from the viewpoint of the provider, the detailed identification of work to be completed, and the provisions for regulatory requirements that impact the end users’ businesses are also important elements of an SLA, but not as crucial as the client’sperspective. References: 3: CISA Review Manual (Digital Version), Chapter 5, Section 5.3.1 4: CISA Online Review Course, Module 5, Lesson 3

Toverify the effectivenessof a third-party provider’ssecurity controls, anindependent external audit reportis thestrongestevidence.

Option A (Incorrect):Security configuration documentsare helpful butdo not confirm effectivenesswithout validation.

Option B (Incorrect):Policies and procedures outlineintent, but anaudit confirms actual implementation.

Option C (Correct):External audit reports (e.g., SOC 2, ISO 27001)provideindependent assurancethat security controls are effective.

Option D (Incorrect):Management interviews providequalitativeinsights but arenot objective evidenceof control effectiveness.

 The rules of engagement define the scope, objectives, methodology, deliverables, and limitations of the penetration testing. They also specify the legal and ethical boundaries, communication channels, and escalation procedures. Establishing the rules of engagement is the first step when planning to conduct penetration testing for a client, as it ensures that both parties agree on the expectations and outcomes of the testing. The other options are important steps, but they should be done after the rules of engagement are established. References: CISA Review Manual (Digital Version) 1, page 381.

 During an audit of a reciprocal disaster recovery agreement between two companies, the IS auditor would be most concerned with the allocation of resources during an emergency. A reciprocal disaster recovery agreement is an arrangement by which one organization agrees to use another’s resources in the event of a business continuity event or incident. The IS auditor would need to ensure that both parties have clearly defined their roles and responsibilities, their resource requirements, their priority levels, their communication channels, and their escalation procedures in case of a disaster. The IS auditor would also need to verify that both parties have tested their agreement and have updated it regularly to reflect any changes in their business environments. The frequency of system testing is not as critical as the allocation of resources during an emergency, because system testing can be performed periodically or on demand, while resource allocation is a dynamic and complex process that requires careful planning and coordination. The differences in IS policies and procedures are not as critical as the allocation of resources during an emergency, because both parties can agree on common standards and protocols for their disaster recovery operations, or they can adapt their policies and procedures to suit each other’s needs. The maintenance of hardware and software compatibility is not as critical as the allocation of resources during an emergency, because both parties can use compatible or interoperable systems, or they can use virtualization or cloud computing technologies to overcome any compatibility issues. References: ISACACISA Review Manual 27th Edition, page 281

The best answer is B. Senior management.

The culture that supports an effective internal control system is set from the top. ISACA’s governance and culture guidance consistently treats culture as a management and leadership responsibility. Senior leadership establishes tone, values, expectations, accountability, and behavioral norms that shape how controls are designed, followed, and enforced across the enterprise. A strong control culture depends on visible commitment from leadership, not just procedural ownership by operational teams.

Option A. HR supports the culture through hiring, training, and policy reinforcement, but HR does not have primary accountability for the overall control environment.

Option C. Line management plays an important role in day-to-day control execution, but enterprise culture is primarily driven by senior leadership.

Option D. Internal audit evaluates and provides assurance over the control system; it does not own or establish the control culture because doing so would impair independence.

Therefore, B is the correct answer because senior management is primarily accountable for establishing the tone and culture that enable an effective and efficient internal control system.

References (Official ISACA):

ISACA Journal, Auditing Your Organizational Culture.

ISACA Now Blog, Culture as a Corporate Asset.

ISACA Digital Video/Podcast, Understanding and Assessing Organization Culture.

ISACA Journal, Auditing Culture.

The IS auditor’s best course of action is to evaluate the implemented control to ensure it mitigates the risk to an acceptable level. This is because the objective of a follow-up audit is to verify that corrective actions have been accomplished as scheduled and that theyare effective in preventing orminimizing future recurrence1. If senior management has implemented a different remediation action plan than what was previously agreed upon, the IS auditor should assess whether the alternative control is adequate and appropriate for the situation. Requesting justification from management for not implementing the recommended control (option D) may be a secondary step, but it is not the best course of action. Reporting the deviation by the control owner in the audit report (option A) may be premature and unnecessary if the implemented control is satisfactory. Canceling the follow-up audit and rescheduling for the next audit period (option C) is not advisable, as it would delay the verification of the effectiveness of the implemented control and potentially expose the organization to further risks. References: 1: Follow-up Audits - Canadian Audit and Accountability Foundation

Comprehensive and Detailed Explanation:

The primary purpose of vulnerability assessments is to identify known weaknesses before they can be exploited by attackers.

Option A: Security awareness is a benefit but not the main purpose.

Option C: Improving posture is an outcome, not the direct purpose.

Option D: Protection against threats is broader than vulnerability assessment.

???? ISACA Reference: CISA Review Manual 27th Edition, Domain 5, section on vulnerability management and assessments.

A three-way match is a process of verifying that a purchase order, a goods receipt and an invoice are consistent before making a payment1. A three-way match ensures that the organization only pays for the goods or services that it ordered and received, and that the prices and quantities are accurate. A three-way match can prevent errors, fraud and overpayments in the accounts payable process.

An IS auditor should use a purchase order when verifying a three-way match has occurred in an enterprise resource planning (ERP) system. A purchase order is a document that authorizes a purchase transaction and specifies the items, quantities, prices and terms of the order2. A purchase order is the first document in the three-way match process, and it serves as the basis for comparing the goods receipt and the invoice. An IS auditor can use a purchase order to check if the ERP system has correctly recorded, matched and approved the three documents before making a payment.

The other options are not as useful for verifying a three-way match. A bank confirmation is a document that verifies the balance and activity of a bank account3. A bank confirmation can be used to confirm that a payment has been made or received, but it does not provide information about the details of the purchase transaction or the three-way match process. A goods delivery notification is a document that informs the buyer that the goods have been shipped or delivered by the seller4. A goods delivery notification can be used to track the status of the delivery, but it does not provide information about the quantity or quality of the goods or the invoice amount. A purchase requisition is a document that requests authorization to purchase goods or services from a specific supplier2. A purchase requisition can be used to initiate the purchasing process, but it does not provide information about the actual purchase order, goods receipt or invoice.

The correct answer is D. Establish a global IT risk scoring criteria.

When business units use different risk methods, their risk scores are not comparable. One unit’s “high” risk may not mean the same thing as another unit’s “high” risk. The organization first needs a common risk scoring method so IT risks can be measured, compared, aggregated, and reported consistently across the enterprise.

Option A is not the best first approach because a weighted score is only useful after the organization has consistent scoring criteria. Option B is not appropriate because choosing the highest-rated risk may overstate overall risk appetite and may be based on inconsistent rating methods. Option C is also inappropriate because averaging inconsistent risk scores can produce misleading results.

ISACA’s glossary defines risk appetite as the amount of risk an entity is prepared to accept when pursuing its objectives. ISACA also discusses risk appetite in terms of identifying risk the organization is or is not willing to accept in relation to its values, digital strategy, stakeholder impact, and required actions.

This maps to Governance and Management of IT because risk appetite, IT risk management, risk reporting, and governance decision-making are Domain 2 topics in the CISA Exam Content Outline.

The correct answer is B. An assessment of how senior management evaluates IT portfolio performance.

An IT metrics dashboard should provide management with meaningful performance information about IT initiatives, services, investments, and portfolios. In a governance context, IT metrics are used to monitor whether IT activities and investments are delivering value and supporting organizational objectives. ISACA explains that metrics are a monitoring mechanism that help management monitor achievement of business-related and IT-related goals. ISACA also states that appropriate metrics help the governing body provide direction based on defined goals and evaluation of metrics.

Option A is too broad because an IT dashboard should not merely show how the IT department is evaluated as a department; it should provide performance information that supports governance decisions. Option C is incorrect because identifying controls needed to mitigate risks is more related to a risk/control assessment, not an IT metrics dashboard. Option D is incorrect because business-process assessment is broader than an IT metrics dashboard and would normally be part of business process review or process improvement.

This question maps mainly to Governance and Management of IT, because ISACA’s CISA Exam Content Outline includes IT governance, IT performance monitoring and reporting, IT resource management, and evaluation of IT project and portfolio management alignment with organizational objectives.

Audit findings should be communicated as early as possible to avoid misunderstandings, provide an opportunity for corrective action, and ensure transparency.

Option A (Incorrect):The planning phase involves defining audit scope, objectives, and methodology, but findings are not yet available to discuss with management.

Option B (Incorrect):The reporting phase formalizes audit results, but discussing issuesonlyat this stage may lead to delays in corrective action.

Option C (Incorrect):The follow-up phase ensures that management has implemented corrective actions, but this occursafterthe initial discussion of findings.

Option D (Correct):The fieldwork phase is when auditors activelygather evidence, analyze data, and identify issues. Discussing observationsduringthis phase allows for immediate clarification, validation, and resolution of misunderstandings before the final report.

Open-source solutions provide flexibility and reduce vendor lock-in, allowing organizations to modify, enhance, and support software independently.

Option A (Incorrect):Open-source software often lacksformalizedsupport levels compared to proprietary solutions, which provide structured SLAs (Service Level Agreements).

Option B (Incorrect):While some open-source solutions are user-friendly, implementation complexity depends on the software and required customization.

Option C (Correct):A key benefit of open-source solutions is thefreedom from vendor dependence. Organizations can customize the software, hire independent developers, or switch providers without being locked into a specific vendor ' s ecosystem.

Option D (Incorrect):Security in open-source software depends on the community and organization managing the solution. Some open-source tools have excellent security, while others may require additional hardening.

Quarterly steering committee meetings best demonstrate alignment of the IT department with the corporate mission because they provide a regular forum for strategic planning, decision making, and communication between IT leaders and business stakeholders12. Steering committee meetings help to ensure that IT goals and initiatives are aligned with the business vision, mission, and objectives, and that IT performance and value are monitored and evaluated34.

References

1: IT Governance and the Balanced Scorecard - ISACA Journal

2: IT Steering Committee Best Practices: A Recipe for Success

3: What is IT Governance? - Definition from Techopedia

4: CISA Cybersecurity Strategic Plan | CISA

The most important validation point is whether the VM replication process is periodically tested to confirm that recovery will actually work. ISACA guidance on backup and recovery states that when using new backup methodologies or technologies, management should test the data afterward to ensure the process is reliably recording all required data, and auditors should ensure periodic health checks are performed.

Option B is correct because recovery adequacy is not proven by the mere existence of replication. ISACA specifically warns that replication alone can increase risk, since corruption can be replicated as well, and it emphasizes validating the reliability of the backup or replication process through testing and health checks.

Option A is important for resilience, but offsite location alone does not prove recoverability. A replica that is never tested may still fail when needed.

Option C is not the most important factor for evaluating recovery procedures. Load balancing supports performance and availability, but it is not the key evidence that replicated systems can be recovered successfully.

Option D is a useful security precaution. ISACA does note that VM backup administrators should not have Internet access to reduce ransomware exposure, but that is a security-hardening issue, not the primary validation of recovery adequacy.

Therefore, B is the best answer because periodic testing is the most important way to validate that VM replication will support actual recovery.

References (Official ISACA):

ISACA Journal, IS Audit Basics: Backup and Recovery — replication can increase risk if corruption is copied; auditors should ensure backup/recovery processes are tested and health checks are performed.

ISACA Journal, A Five-Layer View of Data Center Systems Security — disaster recovery design should consider criticality and RPO/RTO.

Requiring visitors to present identification and pre-approval documents before entering a data center is a preventive control because its purpose is to stop unauthorized access before it occurs. In CISA-style control classification, a preventive control is designed to avoid an incident or reduce the likelihood of an undesirable event. Screening visitors before access is granted is a classic example of prevention.

Option B is correct because the control is applied before access is granted. It is intended to prevent unauthorized individuals from entering the facility. The control does not primarily detect an event after it happens, nor does it correct a problem after occurrence.

Option A is tempting because visitor procedures are often documented in administrative policies, but the question asks for the type of control implemented in this scenario. The specific mechanism described is an entry-screening measure that functions preventively. In exam logic, when asked to choose between functional control types such as preventive, detective, and corrective, the answer should reflect what the control actually does.

Option C is incorrect because a corrective control acts after an incident to restore or remedy conditions. Visitor ID checks do not correct anything after a breach.

Option D is incorrect because a detective control identifies or alerts after or during an event, such as logs, CCTV review, or alarms. Here, the main purpose is to prevent unauthorized access before entry.

So the best answer is B, since requiring ID and pre-approval documents at the entrance is designed to prevent unauthorized physical access to the data center.

References (Official ISACA):

ISACA, Differentiating Key Terms in the Information Security Hierarchy — standards and controls can prescribe required behaviors and control actions.

ISACA Journal, Information Systems Security Audit: An Ontological Framework — supports functional security control categories.

ISACA Journal, IS Audit Basics: Innovation in the IT Audit Process — supports use of standard ISACA terminology in control evaluation.

A business impact analysis (BIA) is a process that identifies and evaluates the potential effects of disruptions to critical business operations as a result of a disaster, accident or emergency. A BIA should include an inventory of relevant business processes that support the organization’s strategic objectives and are essential for its continuity. The inventory should also identify the dependencies, interdependencies, recovery priorities and time frames for each business process. Policies for business procurement, documentation of application configurations and results of business resumption planning efforts are not as useful as an inventory of relevant business processes for performing a BIA. References:

 Business Impact Analysis (BIA) Definition

 Business Impact Analysis (BIA) | ISACA

A risk assessment must be completed as part of annual audit planning. ISACA’s ITAF-based guidance states that the IS audit and assurance function shall use an appropriate risk assessment approach and supporting methodology to develop the overall IS audit plan and determine priorities for effective allocation of audit resources.

Option C is correct because audit planning is fundamentally risk-based under ISACA guidance. Annual planning requires identifying and prioritizing risk areas so the audit plan focuses on the areas of greatest significance. ISACA also notes that, before creating the annual audit plan, the organizationwide risk register should be reviewed thoroughly to prioritize risk areas.

Option A may inform audit planning in some organizations, but it is not a universal required planning step.

Option B can be useful, but it is optional and supplementary, not mandatory.

Option D is typically developed at the engagement level for specific audits rather than as a mandatory organizationwide annual planning deliverable.

Therefore, C is the best answer because risk assessment is the required foundation of the annual audit plan under ISACA guidance.

References (Official ISACA):

ISACA Journal, Developing the IT Audit Plan Using COBIT 2019 — ITAF requires an appropriate risk assessment approach to develop the overall IS audit plan.

ISACA Journal, Auditing and Digital Transformation Are at a Crossroads — before creating the annual audit plan, the organizationwide risk register should be reviewed thoroughly.

ISACA, Certification Exam Candidate Guide — includes evaluation of audit processes and quality programs, supporting structured audit planning.

The correct answer is B. Multiple overwriting.

When storage media will be reused, the goal is to remove sensitive data while keeping the media physically usable. Multiple overwriting writes new patterns of data over existing data so the previous sensitive information is no longer practically recoverable. ISACA describes overwriting as placing an additional layer of information over existing material, with the purpose of protecting the information while not damaging the hard drive itself.

Option A is not correct because cross-cut shredding physically destroys the media. It may be appropriate when media will be disposed of, but not when the storage device must be reused. Option C is not correct because repartitioning changes the disk structure but does not securely erase the underlying data. Option D is not correct because reformatting may remove file system references but often does not securely eliminate recoverable data.

A useful CISA exam point is this:

For reuse, choose logical sanitization such as overwriting.

For disposal, choose physical destruction, degaussing, or shredding depending on the media type and sensitivity.

ISACA notes that common digital data destruction methods include overwriting, degaussing, and physical destruction. Since degaussing and physical destruction generally make media unsuitable for normal reuse, overwriting is the best answer in this question.

The correct answer is C. Hash values.

Hash values are the best way to establish that digital evidence remains unchanged. A hash is a fixed value mathematically generated from data. If even a small change is made to the evidence, the hash value changes. Therefore, comparing the hash value calculated when evidence was collected with the hash value calculated later helps prove whether the evidence is still in its original form.

ISACA’s glossary defines hashing as a cryptographic process that converts input data into a fixed-length hash value, ensuring data integrity and authentication. This directly supports the use of hash values to verify that digital evidence has not been altered.

Option A is not the best answer because imaging creates a forensic copy of the media, but the image still needs to be validated using hash values. Option B helps prevent accidental or intentional modification during examination, but it does not by itself prove the evidence is unchanged. Option D is important because chain of custody documents who handled evidence, when, and how it was protected. However, chain of custody is a procedural control; hash values provide the stronger technical proof of integrity. ISACA defines chain of custody as the evidence-handling process needed to maintain evidence validity and integrity, including documentation of who had access to the evidence and when.

This question maps mainly to Information Systems Auditing Process because it concerns audit evidence reliability, digital evidence handling, and support for audit conclusions. ISACA’s CISA Exam Content Outline includes audit evidence collection techniques and reporting under Domain 1.

Following a breach, the maximum amount of time before customers must be notified that their personal information may have been compromised depends on the industry regulations that apply to the organization. Different industries and jurisdictions may have different legal and regulatory requirements for breach notification, such as the General Data Protection Regulation (GDPR) in the European Union, the Health Insurance Portability and Accountability Act (HIPAA) in the United States, or the Personal Information Protection and Electronic Documents Act (PIPEDA) in Canada. Industry standards, incident response plans, and information security policies are not as authoritative as industry regulations in determining the breach notification time frame. References: CISA Review Manual (Digital Version), [ISACA Privacy Principles and Program Management Guide]

The correct answer is D. Performing a bank reconciliation.

A duplicate payment is a transaction-processing error that affects financial completeness and accuracy. A bank reconciliation is the best compensating control among the options because it compares the organization’s payment records with actual bank activity and helps identify duplicate or incorrect payments after processing.

Option A is not the best answer because manually receipting payments is inefficient and does not reliably detect duplicate outgoing payments. Option B is not correct because hash totals are usually nonfinancial totals used to check processing completeness, such as account number totals, and would not effectively identify duplicate payments. Option C may help detect differences in batch totals, but duplicate online payments can still occur unless the reconciliation identifies the actual duplicate disbursement or settlement.

ISACA has discussed duplicate payment detection as an internal control concern and notes that automated controls can detect duplicate and fraudulent transactions across complete data sets. That supports the control principle that duplicate payments require detective/reconciliation controls, not merely basic totals.

The major concern with the situation where security incidents are resolved and closed, but root causes are not investigated, is that vulnerabilities have not been properly addressed. Vulnerabilities are weaknesses or gaps in the security posture of an organization that can be exploited by threat actors to compromise its systems, data, or operations. If root causes are not investigated, vulnerabilities may remain undetected or unresolved, allowing attackers to exploit them again or use them asentry points for further attacks. This can result in repeated or escalated security incidents that can cause more damage or disruption to the organization.

The other options are not as major as the concern about vulnerabilities, but rather secondary or related issues that may arise from the lack of root cause analysis. Abuses by employees have not been reported is a concern that may indicate a lack of awareness, accountability, or monitoring of insider threats. Lessons learned have not been properly documented is a concern that may indicate a lack of improvement, learning, or feedback from security incidents. Security incident policies are out of date is a concern that may indicate a lack of alignment, review, or update of security incident processes.

Source code synchronization is the process of ensuring that the source code and the object code (the compiled version of the source code) are consistent and up-to-date1. When program changes are implemented, the source code should be recompiled to generate a new object code that reflects the changes. However, if the source code is not recompiled, there is a risk that the object code may be outdated or incorrect. A compensating control is a measure that reduces the risk of an existing control weakness or deficiency2. A compensating control for source code synchronization is to compare the date stamping of the source and object code. Date stamping is a method of recording the date and time when a file is created or modified3. By comparing the date stamping of the source and object code, one can verify if they are synchronized or not. If the date stamping of the source code is newer than the object code, it means that the source code has been changed but not recompiled. If the date stamping of the object code is newer than the source code, it means that the object code has been compiled from a different source code. If the date stamping of both files are identical, it means that they are synchronized.

 Information security policies are high-level statements that define the organization’s approach to protecting its information assets from threats and risks. They should be based primarily on a risk management process, which is a systematic method of identifying, analyzing, evaluating, treating, and monitoring information security risks. A risk management process can help ensure that the policies are aligned with the organization’s risk appetite, business objectives, legal and regulatory requirements, and stakeholder expectations. An information security framework is a set of standards, guidelines, and best practices that provide a structure for implementing information security policies. It can support the risk management process, but it is not the primary basis for defining the policies. Past information security incidents and industry best practices can also provide valuable inputs for defining the policies, but they are not sufficient to address the organization’s specific context and needs. References: Insights and Expertise, CISA Review Manual (Digital Version)

The charging method for IS resources is the way that the IS function allocates its costs to the users or business units that consume its services. The charging method can affect the behavior and incentives of the users and the IS function, as well as the efficiency and effectiveness of the IS resources. Therefore, choosing an appropriate charging method is an important decision for the IS function and its stakeholders.

One of the possible charging methods is to charge specific costs that can be tied back to specific usage. This means that the IS function tracks and measures the actual consumption of each user or business unit for each IS service, and charges them accordingly. For example, if a user uses 10 GB of storage space, 5 hours of CPU time, and 100 MB of network bandwidth, the IS function will charge them based on the unit costs of these resources. This charging method has the advantage of encouraging the most efficient use of IS resources, as it provides clear and accurate feedback to the users about their consumption and costs, and motivates them to optimize their usage and avoid waste or overuse. This charging method also aligns the interests of the IS function and the users, as both parties benefit from reducing costs and improving efficiency.

The other possible charging methods are:

Total utilization to achieve full operating capacity: This means that the IS function charges a fixed amount to each user or business unit based on their proportion of the total operating capacity of the IS resources. For example, if a user or business unit has 10% of the total computing power allocated to them, they will pay 10% of the total IS costs. This charging method has the disadvantage of discouraging efficient use of IS resources, as it does not reflect the actual consumption or usage of each user or business unit, and does not provide any incentive to reduce costs or improve efficiency. This charging method also creates a mismatch between the interests of the IS function and the users, as the IS function benefits from increasing costs and capacity, while the users bear the burden of paying for them.

Residual income in excess of actual incurred costs: This means that the IS function charges a markup or profit margin on top of its actual incurred costs to each user or business unit.For example, if a user or business unit consumes $100 worth of IS resources, the IS function will charge them $120, where $20 is the residual income for the IS function. This charging method has the disadvantage of discouraging efficient use of IS resources, as it increases the costs for the users and reduces their value for money. This charging method also creates a conflict between the interests of the IS function and the users, as the IS function benefits from increasing costs and profits, while the users suffer from paying more than they should.

Allocations based on the ability to absorb charges: This means that the IS function charges different amounts to different users or business units based on their ability to pay or their profitability. For example, if a user or business unit is more profitable or has a higher budget than another user or business unit, they will pay more for the same amount of IS resources. This charging method has the disadvantage of discouraging efficient use of IS resources, as it does not reflect the actual consumption or usage of each user or business unit, and does not provide any incentive to reduce costs or improve efficiency. This charging method also creates an unfair and arbitrary distribution of costs among the users or business units, as some paymore than others for no valid reason. References: 1: Charging Methods for IT Services - IT Process Wiki 2: IT Chargeback Methods - CIO Wiki 3: IT Chargeback - Wikipedia

 An external assessment of network vulnerability is a process of identifying and evaluating the weaknesses and risks that affect the security and availability of a network froman outsider’s perspective. The most important factor to verify during this process is the completeness of network asset inventory, which is a list of all the devices, systems, and software that are connected to or part of the network. A complete and accurate network asset inventory can help identify the scope and boundaries of the network, the potential attack vectors and entry points, the critical assets and dependencies, and the existing security controls and gaps. Without a complete network asset inventory, an external assessment of network vulnerability may miss some important assets or vulnerabilities, leading to inaccurate or incomplete results and recommendations.

Access to production source and object programs is the best way to ensure that effective change management is in place in an IS environment, as it prevents unauthorized or accidental changes to the production code that could affect the functionality, performance, or security of the system. Access to production source and object programs should be restricted to authorized personnel only, and any changes should follow a formal change management process that includes documentation, approval, testing, and review.

References

ISACA CISA Review Manual, 27th Edition, page 254

Change Management Best Practices for the Engineering and …

Change Management - an overview | ScienceDirect Topics

The best way to ensure data integrity across system interfaces is to perform reconciliation. Reconciliation is the process of comparing and verifying the data from different sources or systems to ensure that they are consistent, accurate, and complete. Reconciliation can help to identify and resolve any discrepancies, errors, or anomalies in the data that could affect the quality, reliability, or validity of the information. Reconciliation can also help to detect and prevent any unauthorized or fraudulent data manipulation or modification. References:

CISA Review Manual (Digital Version)

CISA Questions, Answers and Explanations Database

The type of review that is most important to conduct when an IS auditor is informed that a recent internal exploitation of a bug has been discovered in a business application is C. Forensic audit. A forensic audit is a type ofaudit that involves collecting, analyzing, and preserving evidence of fraud, corruption, or other illegal or unethical activities1. A forensic audit can help the IS auditor to identify and document the source, scope, and impact of the exploitation, as well as the perpetrators, motives, and methods involved. A forensic audit can also help the IS auditor to provide recommendations for preventing or mitigating future exploitations, and to support any legal actions or investigations that may arise from the incident2.

The activity most likely to increase internal audit quality is increasing audit staff training. ISACA’s resources on audit capability and internal audit development consistently emphasize building knowledge and skills as a way to improve audit effectiveness and quality. Training strengthens auditors’ technical competence, professional judgment, and ability to identify emerging and atypical risks.

Option A is correct because better-trained auditors are more capable of planning effectively, gathering reliable evidence, assessing controls, and producing useful findings. ISACA training resources emphasize foundational and practical audit knowledge, while reskilling guidance highlights the need for internal audit to improve capability in response to changing risks.

Option B is not the best answer because outsourcing may or may not improve quality; it depends on the provider and governance over the arrangement. It is not inherently more effective than developing internal capability.

Option C is incorrect because increasing the number of planned audits can easily reduce quality if resources are stretched thinner. More volume does not automatically mean better audit work.

Option D can support continuous improvement, but client surveys are an indirect feedback tool. They do not improve technical audit quality as directly as stronger auditor training and competency.

Therefore, A is the best answer because improving auditor competence through training is the most direct and reliable way to increase internal audit quality.

References (Official ISACA):

ISACA, IT Audit Fundamentals Certificate — emphasizes foundational audit concepts and practical application of audit principles.

ISACA Journal, Reskilling Internal Audit — highlights the need for internal audit to improve capabilities to identify emerging and atypical risk.

ISACA Now Blog, Internal Auditing With an Agile Scrum Approach — collaboration and feedback can improve quality and relevance, but competence remains foundational.

A firewall is a device or software that monitors and controls the incoming and outgoing network traffic based on predefined rules. A firewall can help protect an organization’s network and information systems from unauthorized or malicious access, by filtering or blocking unwanted or harmful packets. The most important thing for an IS auditor to verify when evaluating an organization’s firewall is that the logs are being collected in a separate protected host. Logs are records of events or activities that occur on a system or network, such as connections, requests, responses, errors, and alerts. Logs can provide valuable information for auditing, monitoring, troubleshooting, and investigating security incidents. However, logs can also be tampered with, deleted, or corrupted by attackers or insiders who want to hide their tracks or evidence of their actions. Therefore, it is essential that logs are stored in a separate host that is isolated and secured from the network and the firewall itself, to prevent unauthorized access or modification of the logs. Automated alerts are being sent when a risk is detected is a good practice for enhancing the security and efficiency of a firewall, but it is not the most important thing for an IS auditor to verify, as alerts may not always be accurate, timely, or actionable. Insider attacks are being controlled is a desirable outcome for a firewall, but it is not the most important thing for an IS auditor to verify, as insider attacks may involve other factors or methods that bypass or compromise the firewall, such as social engineering, credential theft, or physical access. Access to configuration files is restricted is a critical control for ensuring the security and integrity of a firewall, but it is not the most important thing for an IS auditor to verify, as configuration files may not reflect the actual state or performance of the firewall. 

The performance and reliability of a job scheduling tool can be significantly affected if maintenance patches and the latest enhancement upgrades are missing1. These patches and upgrades often contain fixes for known issues and improvements to the tool’s functionality. If they are not applied, the tool may continue to exhibit known problems or fail to benefit from enhancements that could improve its performance and reliability1. While factors like administrator password requirements23, number of support staff45, and tool classification64 can impact various aspects of a tool’s operation, they are less likely to be the direct cause of performance and reliability problems.

 A disaster recovery plan (DRP) is a set of detailed, documented guidelines that outline a business’ critical assets and explain how the organization will respond to unplanned incidents. Unplanned incidents or disasters typically include cyberattacks, system failures, power outages, natural disasters, equipment failures, or infrastructure damage1. A DRP aims to minimize the impact of a disaster on the business continuity, data integrity, and service delivery of the organization. A DRP also helps the organization recover from a disaster as quickly and efficiently as possible.

A DRP should include steps for obtaining replacement supplies, as this is an essential part of restoring the normal operation of the organization after a disaster. Replacement supplies may include hardware, software, data, network components, office equipment, or other resources that are needed to resume the business functions and processes that were disrupted by the disaster. Obtaining replacement supplies may involve contacting vendors, suppliers, or partners; activating backup or alternative systems; or purchasing or renting new equipment. A DRP should identify the sources, locations, and costs of the replacement supplies, as well as the procedures and responsibilities for acquiring and installing them.

The other three options are not steps that a DRP should include, as they are either part of the pre-disaster planning process or not directly related to the disaster recovery objectives. Assessing and quantifying risk is a step that should be done before creating a DRP, as it helps identify the potential threats and vulnerabilities that could affect the organization and determine the likelihood and impact of each scenario2. Negotiating contracts with disaster planning consultants is also a pre-disaster activity that may help the organization design, implement, test, and maintain a DRP with external expertise and guidance3. Identifying application control requirements is not a step in a DRP, but rather a part of the application development and maintenance process that ensures the quality, security, and reliability of the software applications used by the organization.

Therefore, obtaining replacement supplies is the correct answer.