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
47
Global health score
Critical F
out of 100
Out of support: −10 pointsMicrosoft support for this version (mainstream and extended) has ended: the overall score loses 10 points, then cannot exceed 79 ("Fair" band). A declared ESU does not change the score.
First audit — no trend yet
Audit performed on 18 September 2026
Document generated on 25 September 2026
Collector 4.12.0
SQL Audit Platform SRV-APP-01

Management summary — Remediation

25 check(s) not applicable to SQL Server 2016 — Details at the end of the report.

47
Global health score
Critical F
Out of support: −10 pointsMicrosoft support for this version (mainstream and extended) has ended: the overall score loses 10 points, then cannot exceed 79 ("Fair" band). A declared ESU does not change the score.
First audit — no trend yet
Security
48/100
Performance
83/100
Resilience
53/100
Operations
65/100
Microsoft support SQL Server 2016 — Support ended — July 2026. Paid ESU possible until July 2029, except Express.
To fix: 32 open gap(s), 19 of them priority items (critical + high)
10Critical
9High
6Medium
1Low
First audit — no history yet to measure progress against.
90
Technical security posture — CIS SQL Server L1 (sample)
55 compliant control(s) out of 61 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 log backups every 15-60 minutes depending on RPO
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).
SQL Audit Platform SRV-APP-01

Checks not applicable and not evaluated

Neither gaps nor passes: a not-applicable check does not exist on this version or edition, or examines a feature the instance does not use; a not-evaluated check could not be read (rights, network, missing data).

Not applicable to SQL Server 2016 (25)

CheckTitleReason
AG012REQUIRED_SYNCHRONIZED_SECONDARIES_TO_COMMIT misconfiguredSQL Server version
AG027Contained availability group system databasesSQL Server version
DATA001Sensitive data classification appliedSQL Server version
DATA002Likely PII columns not classifiedSQL Server version
DATA004UNMASK granted narrowlySQL Server version
DATA007Always Encrypted enclave/attestationSQL Server version
DATA008Ledger enabled (integrity required)SQL Server version
DATA009Ledger digest verificationSQL Server version
DBLVL006VECTOR data type inventory (SQL Server 2025)SQL Server version
DBLVL007Native JSON data type inventory (SQL Server 2025)SQL Server version
DBSET010PREVIEW_FEATURES enabled on a database (SQL Server 2025)SQL Server version
DBSET011Accelerated Database Recovery (ADR) disabledSQL Server version
PERF009Optimized locking not enabled (SQL Server 2025 - recommendation)SQL Server version
POST001CLR strict security (inventory)SQL Server version
POST003Trusted assemblies trackedSQL Server version
QOPT004PSP optimization disabled (2022)SQL Server version
QOPT006DOP/CE feedback disabled (2022)SQL Server version
QS007QS Wait Stats captureSQL Server version
SEC022External REST invocation enabled (external rest endpoint enabled)SQL Server version
SEC023External AI runtimes enabled (external AI runtimes enabled - local ONNX)SQL Server version
SEC024External AI models declared (sys.external_models - outbound data flows)SQL Server version
SEC025Server-scoped credentials allowed (allow server scoped db credentials)SQL Server version
SURF016CLR strict security enabledSQL Server version
TDB003Memory-optimized TempDB metadataSQL Server version
TDB005XTP growth (HkTempDB) in TempDBSQL Server version