A logging and monitoring audit shows whether you would see an attack
Logs are the record of what happened. When a server, firewall or Microsoft 365 tenant is not logging, or logs are overwritten after a few days, an investigation has nothing to work with and an insurer or regulator will ask why.
This audit reviews your log sources, retention, alert rules and response steps, with or without a SIEM, and shows the gaps in order of risk.
It is built for IT managers, security leads and owners who want to know whether an attack would be noticed, and for businesses that must show audit logging and monitoring to an auditor, insurer or customer.
This is a focused review of one control area. The Internal Security Audit covers physical, logical and administrative controls together.

What the logging, monitoring and SIEM audit reviews
Log sources
Servers, domain controllers, firewalls, switches, endpoints, Microsoft 365 and cloud services.
Retention
How long logs are kept, where, and whether that meets your obligations.
Time and integrity
Time synchronization, protection from tampering and who can delete logs.
Alert rules
Which events raise an alert, and which important events raise none.
Response
Who receives alerts, how they escalate and how quickly they are handled.
SIEM and tools
Coverage, health and tuning of your SIEM or log management platform.
Logging and monitoring gaps this audit is designed to find
Important systems that log nothing
Firewalls, domain controllers or cloud services that never send their logs anywhere.
Logs that overwrite themselves
Default log sizes that keep only a few days of history on a busy server.
Audit settings left at default
Sign-in, privilege and change events that are simply not recorded.
Alerts with no owner
Rules that fire into a mailbox or dashboard nobody watches.
Noise that hides the signal
So many low-value alerts that the important ones are ignored.
Logs an attacker can erase
Administrators, or a compromised account, able to clear the only copy.
Checks and the evidence behind them
Every conclusion in the report traces back to evidence. For each control we state what we checked, what we reviewed and what we found.
| Control | What we check | Evidence we review |
|---|---|---|
| Coverage | Critical systems send logs | Log source list compared with asset list |
| Audit policy | The right events are recorded | Audit policy and logging settings |
| Retention | Logs are kept long enough | Retention settings and storage reports |
| Alerting | High-risk events raise an alert | Alert rules and recent alert history |
| Response | Alerts are acknowledged and closed | Tickets, escalation list and on-call steps |
| Protection | Logs cannot be quietly deleted | Access rights on log storage |
What you receive from the logging, monitoring and SIEM audit
| Deliverable | What it contains | Who uses it |
|---|---|---|
| Executive report | What you can and cannot see today, the main blind spots and the decisions needed | Owners and executives |
| Technical findings | Each gap by system, with the evidence and the setting to change | IT team or provider |
| Risk register | Each logging and monitoring finding rated by likelihood and impact, with an owner | IT and compliance |
| Remediation roadmap | What to enable, retain or alert on in 30, 60 and 90 days | IT and leadership |
How this audit supports your requirements
| Framework | Requirement or reference | How the audit helps |
|---|---|---|
| PCI DSS | Requirement 10: log and monitor all access to system components and cardholder data | Shows what is logged, reviewed and retained |
| HIPAA Security Rule | Audit controls and information system activity review | Documents how activity on systems with patient data is recorded and examined |
| NIST CSF 2.0 | Detect function | Maps findings to continuous monitoring and adverse event analysis |
| SOC 2 | System operations and monitoring criteria | Provides evidence that anomalies are detected and acted on |
This audit supports your readiness for these requirements. It is not a certification, attestation or legal opinion.
From first call to a risk-ranked report
Consultation
We confirm what is in scope, who authorizes the review and what you need from it.
Evidence
We collect configuration exports, reports and screenshots with read-only access.
Testing
We test each control against the agreed criteria and confirm exceptions with your team.
Report
You receive the findings ranked by risk, with the fix and an owner for each.
What to have ready
You do not need everything on day one. These items let the audit start quickly:
- A list of your servers, firewalls, cloud services and key applications
- Read-only access to your SIEM or log platform, if you have one
- Current audit and logging settings, or access to read them
- Your alert rules and the list of people who receive alerts
- Any retention requirement from a contract, insurer or regulation
Continue with the audit that fits

Internal Security Audit
Physical, logical and administrative controls in one read-only audit. Fixed price: $3,500.
Internal Security Audit →
Internal audit sample report
See the executive summary, findings, risk register and 30/60/90-day roadmap.
Sample report →
Incident response and outage resilience
Prepare the plan, roles and steps your team follows when an alert is real.
Incident response →Other focused reviews
Each review goes deeper into one control area of the Internal Security Audit. Combine them, or start with the area that worries you most.

Led by Ali Hassani, CISO
OC Security Audit / IT Perfection is led by Ali Hassani, a Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, more than 100 business networks designed, implemented and secured, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA.
Questions about the logging, monitoring and SIEM audit
What does a logging and monitoring audit include?
It reviews log sources, audit settings, retention, time synchronization, log protection, alert rules, response steps and the health of your SIEM or log platform.
Do we need a SIEM for this audit?
No. The audit works with the logging you have today and shows what a SIEM or managed service would need to cover.
Do you monitor our systems after the audit?
No. OC Security Audit is independent and read-only. If you want ongoing operation, IT Perfection can help as a separate engagement.
What do we receive at the end of the logging and monitoring audit?
An executive report, findings by system with the setting to change, a risk register and a 30/60/90-day remediation roadmap.
Is logging included in the Internal Security Audit?
The Internal Security Audit reviews logging and monitoring together with identity, network, backup and governance. This audit is a deeper review of logging, monitoring and SIEM on their own.
How long should we keep logs?
It depends on your obligations. The audit compares your retention with the requirements that apply to you, such as contracts, insurance terms and industry rules.
How much does the logging and monitoring audit cost?
It starts from $3,500. The scope and the fee are agreed in writing before work begins.

Make sure an attack would be seen
Schedule a consultation and we will scope a logging, monitoring and SIEM audit for your environment. Starting from $3,500.
Irvine, Orange County and Southern California on-site; remote nationwide.


