Isaca Certification CISA Reddit Questions

The NEXT step for the IS auditor after noting that an employee who has recently changed roles within the organization still has previous access rights should be to B. determine the reason why access rights have not been revoked. Identifying the cause of this situation is crucial for understanding whether it’s due to oversight, process gaps, or other factors. Once the reason is determined, appropriate corrective actions can be recommended to ensure that access rights are aligned with the employee’s current role and responsibilities1.

The organization’s software inventory is not complete. This finding would be of greatest concern to an IS auditor assessing an organization’s patch management process because:

A software inventory is a list of all the software assets that an organization owns, uses, or manages. A software inventory is essential for effective patch management, as it helps identify the software that needs to be updated, the patches that are available, and the dependencies and compatibility issues that may arise. Without a complete software inventory, an organization may miss some critical patches, expose itself to security risks, and waste resources on unnecessary or redundant patches.

Applications frequently need to be rebooted for patches to take effect. This finding would be of moderate concern to an IS auditor assessing an organization’s patch management process because:

Rebooting applications for patches to take effect is a common and expected practice in some cases, especially for operating system or kernel patches. However, frequent reboots may indicate that the organization is not applying patches in a timely or efficient manner, or that the patches are not well-designed or tested. Frequent reboots may also cause disruption to the business operations and user experience, and increase the risk of data loss or corruption.

Software vendors are bundling patches. This finding would be of low concern to an IS auditor assessing an organization’s patch management process because:

Bundling patches is a practice where software vendors combine multiple patches into a single package or update. Bundling patches can have some advantages, such as reducing the number of downloads and installations, simplifying the patch management process, and ensuring consistency and compatibility among patches. However, bundling patches can also have some disadvantages, such as increasing the size and complexity of the updates, delaying the delivery of critical patches, and introducing new bugs or vulnerabilities.

Testing patches takes significant time. This finding would be of low concern to an IS auditor assessing an organization’s patch management process because:

Testing patches is a vital step in the patch management process, as it helps ensure that the patches are functional, secure, and compatible with the existing software and hardware environment. Testing patches can take significant time, depending on the scope, complexity, and frequency of the patches. However, testing patches is a necessary investment to avoid potential problems or failures that could result from applying untested or faulty patches.

The primary reason an IS auditor should discuss observations with management before delivering a final report is A. Validate the audit observations. This is because discussing the observations with management can help the auditor to ensure that the findings are accurate, complete, and supported by sufficient evidence1. It can also help the auditor to obtain management’s perspective and feedback on the issues and risks identified, and to avoid any misunderstandings or surprises when the final report is issued2.

The correct answer is B. Management’s commitment to information security. Management’s commitment to information security is the most critical factor for the success of an information security program, as it provides the leadership, support, and resources needed to establish and maintain a secure environment. Management’s commitment to information security can be demonstrated by:

Setting the vision, mission, and goals for information security, and aligning them with the organization’s strategies and objectives1.

Establishing and enforcing the policies, standards, and procedures for information security, and ensuring compliance with relevant laws and regulations1.

Allocating sufficient budget, staff, and technology for information security, and investing in training and awareness programs2.

Promoting a culture of security within the organization, and engaging with stakeholders and partners to foster trust and collaboration2.