fbpx

CIMSNex User Guides

System Guides

ISMS Guides
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

 A.8.14 Redundancy of information processing facilities would include:

  1. Redundancy Plan: Documentation of a formal redundancy plan that outlines the organization's approach to ensuring redundancy and fault tolerance for critical information processing facilities.

  2. Redundant Systems: Evidence of redundant information processing facilities, such as backup servers, power supplies, network connections, and storage devices, to ensure continuous operations even in case of failures.

  3. High Availability Architecture: Documentation of the organization's high availability architecture, which may include clustering, load balancing, failover mechanisms, and disaster recovery strategies.

  4. Failover Testing: Records of regular testing and validation of failover mechanisms to ensure they work as intended during real-world scenarios.

  5. Data Replication: Evidence of data replication procedures, such as real-time or near-real-time replication of data between redundant facilities to ensure data integrity and availability.

  6. Backup and Recovery: Documentation of backup and recovery procedures for critical systems and data, including the frequency of backups, storage locations, and restoration processes.

  7. Business Continuity Plan: Integration of redundancy measures into the organization's business continuity plan to ensure continuous service availability during disruptive events.

  8. Physical Security Measures: Evidence of physical security measures in place to protect redundant facilities from unauthorized access and potential threats.

  9. Maintenance and Monitoring: Records of maintenance schedules, monitoring, and regular inspections of redundant systems to identify potential issues before they escalate.

  10. Compliance Documentation: Evidence of compliance with relevant regulations and standards that require redundancy measures for critical information processing facilities.

The purpose of redundancy is to minimize the risk of service interruptions, data loss, and downtime in the event of hardware failures, natural disasters, or other unforeseen incidents. As an auditor, I would review these pieces of evidence to ensure that the organization has taken appropriate measures to maintain redundancy in its information processing facilities, promoting the continuity of operations and safeguarding against potential disruptions.

 

ISMS Guides
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

A.8.15 Logging would include:

  1. Logging Policy and Procedures: Documentation of a policy and procedures that outline the organization's logging practices. The policy should specify what events are logged, the format of logs, retention periods, and access controls to the logs.

  2. Log Configuration Settings: Records of the configuration settings for logging systems, including details of what events are logged, log levels, and log storage locations.

  3. Log Entries: Access to log entries that capture security-relevant events and activities, such as login attempts, privilege escalations, file access, system changes, and other relevant events.

  4. Log Analysis: Evidence of log analysis procedures and tools used to monitor and review log entries for potential security incidents or anomalies.

  5. Regular Review: Records of regular log reviews conducted by authorized personnel to detect unusual or suspicious activities.

  6. Incident Response Logs: Records of security incidents detected through log analysis, including the actions taken to mitigate the incidents and the resolution outcomes.

  7. Compliance Documentation: Evidence of compliance with relevant regulations, standards, and internal policies regarding logging practices and data privacy.

  8. Access Controls: Evidence of access controls in place to ensure that only authorized personnel can access and modify logs.

  9. Training Records: Records of training provided to personnel responsible for logging activities, ensuring they understand their roles and responsibilities in log management and analysis.

  10. Continuous Improvement Efforts: Evidence of ongoing efforts to improve logging practices based on lessons learned from security incidents and changes in the threat landscape.

Effective logging is crucial for monitoring and detecting security events, facilitating incident response, and maintaining an accurate record of system activities. As an auditor, I would assess the presence and effectiveness of these pieces of evidence to ensure that logging practices are in line with industry best practices and that potential security issues are promptly identified and addressed.

ISMS Guides
Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

A.8.16 Monitoring activities would include:

  1. Monitoring Policy and Procedures: Documentation of a policy and procedures that outline the organization's approach to monitoring information systems, networks, and security events. The policy should define the scope of monitoring, the types of activities monitored, and the frequency of monitoring.

  2. Monitoring Tools and Technologies: Evidence of the tools and technologies used for monitoring activities. This may include intrusion detection systems (IDS), intrusion prevention systems (IPS), log management solutions, security information and event management (SIEM) systems, and other monitoring tools.

  3. Configuration Records: Records of the configuration settings for monitoring tools, including details of what is being monitored, thresholds, and alerting mechanisms.

  4. Logs and Reports: Logs and reports generated by monitoring tools that capture and record security events, incidents, and anomalies. These logs should be reviewed regularly to detect any unusual or suspicious activities.

  5. Incident Response Procedures: Documentation of incident response procedures related to monitoring activities. This includes how security incidents are identified, reported, and responded to based on the information collected through monitoring.

  6. Incident Logs: Records of security incidents detected through monitoring activities, including the actions taken to mitigate the incidents and the resolution outcomes.

  7. Compliance Documentation: Evidence of compliance with relevant regulations, standards, and internal policies regarding monitoring activities and data privacy.

  8. Access Controls: Evidence of access controls in place to ensure that only authorized personnel can access monitoring tools and logs.

  9. Training Records: Records of training provided to personnel responsible for monitoring activities, ensuring they understand their roles and responsibilities in monitoring and responding to security events.

  10. Continuous Improvement Efforts: Evidence of ongoing efforts to improve monitoring activities based on lessons learned from security incidents and emerging threats.

Monitoring activities are critical for detecting and responding to security incidents promptly. As an auditor, I would assess the presence and effectiveness of these pieces of evidence to ensure that monitoring activities are implemented in line with best practices and that potential security risks are proactively identified and addressed.

USER GUIDES

Image
SIMPLIFYING IMPLEMENTATION OF ISO STANDARDS, providing specialized guidance through reliable Expert Knowledge and Software to help you obtain and maintain your ISO certification.

More Links

FEATURED STANDARDS

ISO 27001 - Information Security

ISO 20000 - IT Service Management

ISO 22301 - Business Continuity

ISO 9001 - Quality Management

ISO 45001 - Health & Safety

ISO Compliance Software
Integrate . Mantain . Comply

Search