System Guides

Privileged User Management: Evidence of procedures for managing privileged users, such as administrators, who have access to utility programs. This should include user account creation, modification, and termination processes.

Privileged Account Monitoring: Logs and records of privileged account activities, including the use of utility programs. These logs should be regularly monitored for any suspicious or unauthorized activities.

Separation of Duties: Documentation of separation of duties to ensure that users with access to utility programs do not have sole control over critical functions. This helps prevent potential abuses of privileges.

Least Privilege Principle: Evidence of the principle of least privilege being applied, meaning that users are only granted the minimum privileges necessary to perform their job functions, reducing the risk of unauthorized access to utility programs.

Training and Awareness: Records of training programs and awareness initiatives provided to users with access to utility programs. This ensures that they understand their responsibilities and the risks associated with privileged access.

Vulnerability Management: Evidence of regular vulnerability assessments and patch management procedures for the utility programs to mitigate potential security risks.

Incident Response Procedures: Documentation of incident response procedures specific to incidents related to privileged utility program usage. This includes how incidents are identified, reported, and responded to.

Review of Configuration Settings: Verification that utility programs are configured securely and in accordance with industry best practices to prevent misuse.

Compliance Documentation: Evidence of compliance with relevant regulations, standards, and internal policies regarding the use of privileged utility programs.

Software Approval Process: Documentation of a formal software approval process that outlines the steps required to request, review, and approve the installation of new software on operational systems. This process should include security reviews to ensure that the software is safe and compliant with the organization's policies.

Change Management Records: Records of change management processes for software installation, including change requests, approvals, testing, and implementation plans. These records should demonstrate that software installations are controlled and properly authorized.

Licensing Compliance: Evidence of compliance with software licensing agreements, ensuring that all software installed on operational systems is properly licensed and authorized for use.

Vulnerability Management: Documentation of vulnerability management processes that include regular scanning and assessment of installed software for known vulnerabilities. Evidence of patch management procedures for addressing and mitigating identified vulnerabilities.

User Privileges: Verification of user privileges and access controls to ensure that only authorized personnel have the capability to install software on operational systems.

Segregation of Duties: Documentation of segregation of duties to prevent conflicts of interest and unauthorized software installations. Separate roles should be defined for requesting, approving, and installing software.

Software Configuration Baselines: Evidence of established configuration baselines for operational systems, ensuring that software installations adhere to the approved configurations and are consistent across the organization.

Logs and Monitoring: Access logs and monitoring records to track software installations and detect any unauthorized or suspicious activities related to software on operational systems.

Incident Response Procedures: Documentation of incident response procedures specific to software installations, outlining how the organization addresses security incidents related to software vulnerabilities or unauthorized installations.

Training Records: Proof of user training and awareness programs related to software installation procedures and security best practices.

Compliance Documentation: Evidence of compliance with relevant regulations and standards concerning software installations on operational systems.