SQL Audit Platform
SQL Server audit report
Prepared for

SRV-APP-01

production Microsoft SQL Server 2016 (SP3) Standard Edition (64-bit) srv-app-01.atlantique.local
70
Global health score
Fair C
out of 100
First audit — no trend yet
Audit performed on 09 September 2026
Document generated on 23 September 2026
Collector 4.2.0
SQL Audit Platform SRV-APP-01

Management summary — Remediation

70
Global health score
Fair C
First audit — no trend yet
Security
65/100
Performance
96/100
Resilience
75/100
Operations
84/100
To fix: 30 open gap(s), 19 of them priority items (critical + high)
9Critical
10High
7Medium
1Low
First audit — no history yet to measure progress against.
90
Technical security posture — CIS SQL Server L1 (sample)
56 compliant control(s) out of 62 evaluated
These controls also contribute to GDPR (Art. 32) and NIS2 (Art. 21) technical measures.
Conformity rate over the sample of CIS controls tested by the platform — not coverage of the full CIS benchmark.

Top business risks

Translated into business language, ranked by stakes. Risk is expressed as a level (High / Medium / Low) and an effort, with no financial figure.

1
Your backups won't protect you from a failure or an attack Critical

In case of disk failure, corruption or ransomware, you risk losing data with no way to restore it.

Risk level Critical Effort High
Recommended action Schedule full backups at least weekly
2
Your database is exposed to unauthorized access Critical

A security gap can allow theft or leakage of your customer and business data.

Risk level Critical Effort Low
Recommended action Disable the SA account and create dedicated named accounts for the administrators — the SA account is a prime target for brute-force attacks. Quick fix, low risk (check beforehand that no application connects with it).
3
Your database could go down without guaranteed recovery Critical

If your service continuity isn't guaranteed, an outage can halt your operations for hours or days.

Risk level Critical Effort High
Recommended action Run a full integrity check of the database, determine the extent of the corruption, then restore the pages or the database from a healthy backup — untreated corruption leads to data loss. Urgent action, high risk (get expert assistance before attempting any repair).
4
The server configuration deviates from best practices Critical

Unsuitable settings can undermine the stability, security or performance of your database.

Risk level Critical Effort Low
Recommended action Cap the maximum server memory, reserving RAM for the OS (starting rule: total RAM - 4 GB, or - 10% above 16 GB) — without a cap, SQL Server can starve the system and cause swapping. Quick intervention, low risk.
5
Your sensitive data is not encrypted Critical

If files or media are stolen, the data stays readable and GDPR compliance is not ensured.

Risk level Critical Effort High
Recommended action Back up each TDE certificate together with its private key and keep them off-server in a secure vault — without this backup, an encrypted database becomes unrecoverable after a disaster. Quick to do, low risk (be sure to protect the key password).