ISO 27001 Annex : A.12.4 Logging and Monitoring

ISO 27001 Annex : A.12.4 Logging and Monitoring Its objective is recording events and generating evidence.

A.12.4.1 Event Logging

Control- Event logs should be produced, retained, and regularly reviewed to record user activities, exceptions, defects, and information security events.

Implementation Guidance- Where applicable, event logs should include:

IDs of User;
Activities of the system;
dates, times and key events details, such as log-on and log-off;
System ID or location and device recognition where possible;
records of the attempts to access the system successfully as well as rejected ones
successful and unsuccessful data records and other attempts to access resources;
system configuration alterations;
utilization of privileges;
the application and use of systems utilities;
Accessed files and access kinds;
network addresses and protocols;
Entry management system warnings.
Protective mechanisms such as anti-virus and intrusion detection systems are activated and deactivated as required;
Transaction records done in applications by users.

Event logging inspires automatic control systems capable of producing integrated network monitoring notifications and warnings.

Other information- Sensitive information and personally identifiable information can be used in event logs. Proper measures in the field of privacy should be implemented.
System administrators should not be allowed to delete or deactivate logs of their own activities where possible.

A.12.4.2 Protection of Log Information

Control- Logging and log information should be secure from intrusion and unauthorized access.

Implementation Guidance- Controls should be designed to protect against unauthorized log information changes and operational logging problem, including the following:

Alterations to the types of messages recorded;
Editing or removing log files;
The logfile media storage space is surpassed, which means either that an event is not registered or that the past events have been over-written.

Certain audit logs may require archiving as part of the retention of records or as a result of collecting evidence and retention requirements.

Other information- System logs also contain a large amount of information, which is largely unique to monitoring information security. The copying automatically to a second log of relevant message types or the use of suitable device utilities or auditing tools to perform file interrogations and rationalizing should be considered to help classify significant events for information security monitoring.

System logs must be protected, because data can create a false sense of security, when often modified or deleted. To safeguard logs, real-time copy of logs to a system outside the control of a system manager/operator.

Also Read : ISO 27001 Annex : A.12.3 Backup

A well-known ISO 27001 Lead Auditor and ISO 27001 Lead Implementer certificate that mainly covers information security clauses and their implementation, i.e., controls which should be implemented by the organization to preserve the CIA triad, Confidentiality, Integrity, and Availability to maintain their critical, sensitive information in a secure manner. Infosavvy, a Mumbai- based institute, provides multi-domain certifications and training, which include IRCA CQI ISO 27001:2013 Lead Auditor (LA) and ISO 27001 Lead Implementer (LI) (TÜV SÜD Certification). Infosavvy will help you to understand and recognize the full scope of your organization’s security checks to protect your organization’s activities and information equipment (assets) from attacks, and also to illustrate the backup policy to safeguard if data gets lost due to intentional or natural hazards. It also helps in maintaining the logging and monitoring of data transaction records, access records, and other records into protection. We have trainers with extensive expertise and experience to ensure the efficient handling of the security of information. Consequently, the applicant will gain the necessary skills for the ISMS audit by using commonly agreed audit concepts, procedures and techniques

A.12.4.3 Administrator and Operator Logs

Control- The activity of the System Manager and System Operator is to be logged and the logs kept safe and monitored closely.

Implementation Guidance- The logs of the information processing facilities that be manipulated under their direct control by Private user account holders, so it is important to keep logs safe and reviewed to ensure the privileged users are kept accountable.

Other information- A non-controlling system and network administrators can be used to monitor compliance activities of the system and the network management.

A.12.4.4 Clock Synchronization

Control- Clocks in all related information management systems should be integrated into a single reference time source for an organization or safety domain.

Implementation Guidance- Documentation of external and internal time representation requirements, synchronization, and precision. These may be legal, regulatory, contractual, standardized, or internal monitoring requirements. A standard reference time should be defined for use inside the organization.

The organization approach should be documented and implemented to obtain a reference time from an external source and the way internal clocks can be synchronized reliably.

Other Information- Correct clock settings are essential to ensure that audit reports, which may be used for investigation or as proof in legal or disciplinary proceedings, are reliable. Inaccurate audit logs can impede such inquiries and damage their credibility. The main clock for logging systems can be used as a clock linked to the radio time from a national atom. To maintain all servers in sync with the master clock, a network time protocol can be used.

Questions related to this topic

Where are audit logs stored?
ISO 27001 Annex : A.12.4 Logging and Monitoring?
Should audit logs be maintained?
How long should audit logs be kept?
What security events should be logged?
Expalin controls of ISO 27001 Annex : A.12.4 Logging and Monitoring?

ISO 27001 Requirements

Clause 4.1 Understanding the organization and its context

Clause 4.2 Understanding the needs and expectations of interested parties
Clause 4.4 Information security management system
Clause 4.3 Determining the scope of the information security management system
Clause 5.1 Leadership and commitment
Clause 5.2 Policy
Clause 5.3 Organizational roles, responsibilities and authorities
Clause 6.1 Actions to address risks and opportunities
Clause 6.1.2 Information security risk assessment process
Clause 6.1.3 Information security risk treatment
Clause 6.2 Information security objectives & planning
Clause 7.1 Resources
Clause 7.2 Competence
Clause 7.3 Awareness
Clause 7.4 Communication
Clause 7.5 Documented information Implementation Guideline
Clause 8.1 Operational planning & control
Clause 8.2 Information security risk assessment
Clause 8.3 Information security risk treatment
Clause 9.1 Performance evaluation Monitoring, measurement, analysis & evaluation
Clause 9.2 Internal audit
Clause 9.3 Management review
Clause 10.1 Non conformity and corrective action
Clause 10.2 Continual Improvement

ISO 27001 Annex A Controls

About ISO 27002

This Blog Article is posted by
Infosavvy, 5B 306 Riverside Greens, Panvel, Raigad 410206 Maharashtra, India

Contact us – www.infocerts.com

https://goo.gl/maps/mHkyURHmeFXyGiVw5

Upcoming Training :- ISO27001 LA T. D.:-Coming soon.. ISO42001 LI T. D.:-16th,17th Nov 2024.