Practitioner notes on database security, regulatory compliance, and sovereign infrastructure — written for the people responsible for keeping systems secure and running.
18 articles shown
October 7, 2026
A five-area workshop for reviewing access, audit records, sensitive data, monitoring, and recovery, with evidence checks and a method for assigning actions.
Read the articleMoncho
How federated identity, scoped grants, and governed emergency access reduce reliance on copied cluster secrets, with revocation checks to try.
Dorbar
Recording, participant access, and encryption start with the room’s trust model. How Dorbar handles Official rooms and its unreleased Sealed design.
Nothi
A consistent database interface still needs engine-specific recovery paths. What to check in backups, restores, upgrades, and day-two operations.
Vyrell
How account history helps explain unusual database activity, where statistical baselines fall short, and what to ask when reviewing an alert.
Moncho
Follow a Kubernetes add-on from approved digest to admission check, including what image scans and signatures can and cannot establish.
Dorbar
A recorded meeting is a data-protection event. Only a room the server can see can be recorded, and it should record with visible consent, offline transcription, and sensitive-data masking. How to do it defensibly.
Nothi
Most internal database platforms need a code change and a release to support a new engine. Catalog-driven discovery makes it a data change instead: a scanner finds installed operators and offers them, with no redeploy.
Vyrell
Agentless database monitoring reads each engine's own native audit trail through a read-only account, with nothing installed on production. How it works, why a regulated estate prefers it, and its honest limits.
Moncho
'Multi-tenant Kubernetes' spans soft namespace separation to hard cluster-per-tenant isolation. The spectrum, its honest limits, and how to match a tier to the regulatory risk.
Dorbar
For government and regulated buyers, where a meeting lives decides which laws apply and what a breach exposes. The residency questions worth asking, and the answers that hold up.
Nothi
The most dangerous moment for regulated data is a routine deletion that should not have happened. What fail-closed deletion, validated per-engine restore, and an immutable audit trail look like in practice.
Vyrell
A SIEM gives you estate-wide correlation, but it does not understand the database. How database activity monitoring differs, why the two are complementary, and why compliance forces the distinction.
Moncho
A benchmark scan is a snapshot; an auditor wants continuous, tamper-evident evidence mapped to frameworks. The difference between running the CIS Kubernetes Benchmark and producing an evidence pack.
Dorbar
What 'end-to-end encrypted' should and should not mean for a regulated video meeting: the server-trusted model, the sealed model, and how to read a vendor's encryption claim precisely.
Nothi
A framework for regulated teams choosing between a public-cloud managed database and running their own: residency, isolation you can demonstrate, day-two operations, and the honest tradeoffs.
Vyrell
A practitioner's guide to the database controls a Bangladesh Bank ICT examiner expects, from audit trails to privileged-access monitoring, and why an agentless approach fits a regulated estate.
Vyrell
ISO/IEC 27001 is a risk-based management system, not a checklist. What certification really involves, where your databases fit, and why it is not the same as SOC 2, from a company that holds it.
