DMCDMC Bilgi Teknolojileri
🛡️ Built for KVKK & GDPR · Read-only first

Make database security visible.

SentinelDB360 answers one question for enterprise SQL Server: what sensitive data exists, who can access it, what security holes are present, and how do I fix them?

70+ security rules 9 phases end to end 100% read-only default TR / EN reports

Works end to end with the Microsoft data platform

SQL Server 2008–2025 Azure SQL Database Azure SQL Managed Instance Microsoft Entra ID Azure Cosmos DB Azure Key Vault
01 · DISCOVER

Find the sensitive data and its owner

Scans every table and column, recognises even poorly-named columns from the data inside them, and answers “who can reach this?”.

02 · ASSESS

Measure the risk, map to compliance

Turns more than 70 rules into a clear risk score and links every finding to KVKK and GDPR.

03 · FIX

Close it safely and reversibly

Ready apply, validate and rollback commands, plus data masking. Every action is logged.

The problem

Where is your sensitive data, who holds it, how safe is it?

ERP and CRM databases grow over the years. Personal data such as national IDs, IBANs, cards and salaries ends up everywhere, permissions pile up, and wrong settings go unnoticed. KVKK and GDPR ask for control you can prove. SentinelDB360 closes that gap: it finds the data, measures the risk and fixes the holes.

Capabilities

One platform, nine steps

The whole process in one place, from finding the data to safely closing the gap.

🔍

Discovery and classification

Scans every table and column. Finds national IDs, IBANs, credit cards, e-mail, phone and secret keys. It even recognises poorly-named columns from the data inside them.

👥

Access analysis

Clearly answers “who can reach this personal data?”. It works out the real access map across roles, permissions and masking-bypass paths.

🛡️

Security assessment

Checks configuration, privilege, encryption and patch gaps with more than 70 ready-made rules. Every finding comes with its severity, impact and fix.

🧩

Automated fixes

Generates apply, validate and rollback commands for every finding, plus ready-to-run data-masking scripts for each sensitive column.

⚙️

Controlled changes

Changes nothing by default. When you choose to act, it shows the change, asks for approval, applies it safely, validates it and can roll back. Every step is logged.

🤖

AI advisor

Turns technical findings into plain language everyone understands, with priorities and the expected drop in risk. It works without an internet connection too.

📄

Reporting

Executive and technical reports (TR/EN), Excel, the KVKK Personal Data Inventory and signed evidence. Ready to hand to management or an auditor.

📈

Change and trend

Catches anything getting worse since the last scan: a new full-access user, removed masking, a new sensitive column. Shows your security score over time.

🏢

Central management

All customers from one panel: role-based access, each customer’s data kept separate, license tracking and a fleet view.

Transparency

What do we actually mean by “70+ rules”?

No question marks left. Here are the 70 security rules the assessment covers (by category) and the 14 sensitive data types it auto-detects. The full list is open source.

70 security rules, by category

  • 26Access & privilegeWho can reach what; excessive privilege, public/guest, UNMASK, fixed server roles.
  • 19Attack surfacexp_cmdshell, OLE/CLR, linked servers, risky sp_configure switches.
  • 8Database configurationTRUSTWORTHY, ownership chaining, AUTO_CLOSE/SHRINK, ownership.
  • 8Authenticationsa account, blank/weak passwords, password policy and expiry.
  • 4EncryptionTDE (on-disk encryption), backup encryption, certificate expiry.
  • 3AuditingServer audit and the default trace.
  • 2Patch & versionMissing-patch and end-of-life version detection.

Why 70? Because these are the checks that actually matter for SQL Server hardening and KVKK/GDPR. The catalog is data-driven and grows toward 100+ over time.

Request the full rule list →

14 auto-detected sensitive data types

National IDTax NoIBANCredit CardE-mailPhoneAddressSalaryPasswordHashAPI KeySecretTokenUsername

These are recognised not just from the column name but from the actual data inside. For example a checksum for national IDs, mod-97 for IBAN, Luhn for credit cards, caught even when the column is named “col_a”.

See how it looks in the sample reports →
How it works

A thin client collects, the engine assesses

The scanner carries zero business logic; all analysis runs in the secure engine.

🌐 Lite (cloud)

The thin console scanner only collects, end-to-end encrypts the result (.bshscan) and uploads it. All scoring, classification and reporting happen in the portal.

  1. 1 Run the read-only security probes
  2. 2 Encrypt with AES-256-GCM + RSA (public key in the exe)
  3. 3 Upload → decrypt → assess → report

🔒 Full (fully local and licensed)

Collection, analysis and reporting all run in your own environment. It creates its own encrypted repository database. No internet required; it works fully offline.

  1. 1 Machine-bound license (a cryptographic precondition)
  2. 2 Local scan + encrypted at-rest storage
  3. 3 Local branded reports + Apply Mode
Output

Boardroom-ready reports (TR and EN)

Every assessment ships as a corporate PDF: a circular score gauge, severity distribution, the KVKK Personal Data Inventory and signed evidence, in both executive and technical formats and both languages.

SentinelDB360 Executive Summary report cover (score gauge + severity bars)
Executive summary (cover)
SentinelDB360 Technical security report, findings and recommendations
Technical Report
KVKK/GDPR Personal Data Inventory
KVKK Data Inventory
SentinelDB360 Yönetici Özeti report cover (Turkish)
Executive Summary (TR)
Editions

Pick what fits

Lite for a fast assessment. Full for total control and offline environments.

Feature
LiteCloud portal · free
FullLocal · licensed
Sensitive-data discovery & classification
Access analysis & 70+ rules
TR/EN PDF, Excel, KVKK Data Inventory
AI security advisorAzure OpenAILocal (Ollama)
Fully local (offline)
Local encrypted repository & trend
Controlled Apply Mode (rollback + audit)
Central portal & fleet viewOptional push
Security & Compliance

Secure by design, provable compliance

Raw personal data never leaves the environment; every report is audit-ready.

🔐

Raw PII never leaves

In Lite, detection runs on the client; only redacted/hashed evidence is uploaded. In Full, everything is local and AES-256-GCM encrypted at rest.

🧾

Signed audit evidence

Each assessment carries a tamper-proof fingerprint (ScanHash) and a signed document. You can present it to a regulator or auditor.

🗝️

License = cryptographic precondition

In Full the rule catalog is sealed; it cannot be opened without a valid, machine-bound license. Resistant to reverse engineering.

🚦

No production impact

Read-only default + session hardening. Changes happen only in approved Apply Mode, with transactions and tested rollback.

📋 KVKK 🇪🇺 GDPR 🛡️ CIS Benchmark 🔏 Microsoft Security Baseline 📑 KVKK Data Inventory
Who it's for

One source of truth for every role

🧑‍💻

DBA / Sysadmin

Hardening findings and safe, scripted fixes.

🕵️

Security Auditor / CISO

Objective risk score, CIS-mapped evidence and a technical report.

⚖️

KVKK / GDPR (DPO)

Personal-data inventory, exposure and masking bypass.

🎯

Penetration Tester

Attack paths to sensitive data and excessive privileges.

👩‍🔧

Application Developer

Classification (even badly-named columns) and least privilege.

🏛️

Executive / C-level

One headline score and the upside of fixing it.

Assess your database in 30 minutes

Start with a read-only scan; see what sensitive data lives where, who can access it, and how to fix it.

FAQ

Frequently asked questions

Will it harm my production database?
No. The default is 100% read-only with session hardening, so it does not affect production workloads. Changes happen only in the explicitly-approved Apply Mode, with transactions and tested rollback.
Does sensitive data leave the environment?
No. In Lite, raw PII never leaves the customer environment; only redacted/hashed evidence is uploaded. The Full edition runs entirely on-prem and stores data encrypted at rest.
Which SQL Server versions are supported?
Every SQL Server release from 2008 to 2025 (Express, Standard, Enterprise). This includes end-of-life and missing-patch detection. Azure SQL Database and Azure SQL Managed Instance are supported too, with edition-aware rules. Authentication: SQL, Windows and Microsoft Entra ID (including managed identity / service principal). PostgreSQL and MySQL are planned for later releases.
What is the concrete KVKK/GDPR output?
A Personal Data Inventory (KVKK/VERBIS-aligned), an access map, exposure findings, signed audit evidence and ready-to-run remediation scripts.
Does it work air-gapped (offline)?
Yes. The Full edition runs entirely locally; everything, including the AI advisor, can work without internet via a local LLM.