Continuity and IT Controls

Logging, Monitoring and Audit Evidence Management

We define which events are logged from which system, where and for how long they’re kept, and who reviews them how often. We record the date, scope and result of each review.

Logging policyLog sourcesRetention periodTime synchronizationLog reviewMonitoringEvidence

Service definition

What is logging, monitoring and evidence management, and who is it for?

The scope is recording security-relevant events (sign-ins, permission changes, admin actions, access denials, configuration changes), storing the records so they can’t be altered, reviewing them regularly and passing suspicious activity to incident management.

01

Do we have to buy a SIEM?

No. The requirements and review process are defined first; if scale and risk call for it, a SIEM or managed monitoring is recommended. A SIEM nobody looks at is an expensive log store.

02

How long should logs be kept?

It’s set based on legislation, contracts and incident investigation needs; the period is written into the policy with its justification.

03

Are Microsoft 365 logs included?

Yes; audit logs and sign-in records are covered, taking license-dependent retention periods into account.

04

How is a review record kept?

A simple record with the date, reviewer, scope, findings and follow-up actions is enough.

Project stages

How do we proceed?

01 / STAGE

Inventory

Log sources and the current state are identified.

02 / STAGE

Policy

Retention and review rules are written.

03 / STAGE

Process

The review and alert flow is started.

04 / STAGE

Evidence

Records from the first period are organized.

Compliance and Audit

Plan today the records you’ll look for during an incident and an audit

Share your critical systems and current logging infrastructure; let’s scope the policy, review process and evidence structure and prepare a proposal.