The BEST way to validate whether a malicious act has actually occurred in an application is to review:
Click on the arrows to vote for the correct answer
A. B. C. D.C.
The BEST way to validate whether a malicious act has actually occurred in an application is to review activity logs (option C).
Activity logs record all system activities, including user activities, system events, and errors. They provide a detailed record of what has occurred in the system, including who accessed the system, what they did, and when they did it. As such, activity logs are an essential tool for detecting and investigating malicious acts.
Access controls (option B) and segregation of duties (option A) are important security measures to prevent malicious acts from occurring. Access controls restrict access to sensitive information and critical systems to authorized personnel only, while segregation of duties ensures that no single person has too much control over critical processes. However, they are not the best way to validate whether a malicious act has actually occurred.
Change management logs (option D) are used to track changes made to the system, including software updates, configuration changes, and patches. While change management logs can be helpful in identifying unauthorized changes to the system, they do not provide a complete picture of system activity and are not the best way to validate whether a malicious act has occurred.
In summary, activity logs are the BEST way to validate whether a malicious act has actually occurred in an application, as they provide a detailed record of all system activities, including user activities and system events.