Data Governance & Security

    A compliance framework tells you what's missing. It doesn't write the row-level security policy, configure the encryption, or build the deletion pipeline. We engineer the access control, encryption, audit logging, and retention controls that a SOC 2 or HIPAA audit actually tests.

    We work hands-on with: Vault, Okta, PostgreSQL, Snowflake, Terraform, Auth0, Kubernetes.

    Data governance and security engineering builds the row-level security, encryption, and audit logging that a compliance framework requires but doesn't build for you.

    What Data Security Engineering & Governance Actually Involves

    Data security engineering services and data governance consulting build the controls a compliance program requires: sensitive data discovery, data classification, access control at the database (row-level security, column masking), data encryption services and key management, and audit logging and retention pipelines. A compliance framework tells you a control is required. This is the engineering that makes it real, not just documented.

    Most governance failures aren't technical. They're a tool bought and never operationalized. The catalog or policy platform works fine. What's missing is who owns wiring it into the actual database.

    • Discovery: Sensitive data gets classified once in a spreadsheet and never re-scanned as schemas change, so PII ends up in columns nobody flagged.

    • Access control: Permissions get granted ad hoc and rarely revoked, so "least privilege" stays a policy sentence, not a database grant.

    • Encryption & secrets: Static database passwords sit in an env file long after the KMS and Vault setup was budgeted for.

    • Audit & retention: Deletion requests clear the primary table but never reach the replica, the backup, or the cache.

    45% of cloud databases are publicly accessible due to misconfiguration

    Not a sophisticated attack. Nobody engineered the access control before the database went live.

    The assessment we hand you names the exposure up front : where sensitive data actually lives, who can reach it today, what's encrypted, what's logged, and which specific control closes each gap against the framework you're working toward.

    Problems That Trigger This Engagement
    • A SOC 2, HIPAA, or PCI-DSS audit is on the calendar and controls are informal
    • A customer security questionnaire cost you a deal, or nearly did
    • You don't actually know who can access sensitive data in your own database
    • A new privacy regulation now covers data you didn't previously have to protect
    • You bought a governance or catalog tool and never finished configuring it
    • Access requests get handled ad hoc, with no consistent policy behind them

    Match Your Situation to the Fix

    A quick lookup across the four parts of a governance and security engagement.

    Common data governance and security problems mapped to the DharmOps fix
    SituationLikely Solution
    A SOC 2, HIPAA, or PCI-DSS audit is on the calendar and controls are informalAudit Logging, Retention & Deletion Engineering — audit trails that answer who accessed what and when
    A customer security questionnaire cost you a deal, or nearly didEncryption & Secrets Overhaul — field-level encryption and KMS-backed key management
    You don't actually know who can access sensitive data in your own databaseAccess Control Engineering — RBAC/ABAC redesigned around least privilege, enforced at the database
    A new privacy regulation now covers data you didn't previously have to protectSensitive Data Discovery & Classification — scanning production databases for where PII, PHI, or PCI actually lives
    You bought a governance or catalog tool and never finished configuring itSensitive Data Discovery & Classification — classification wired into access policy, not a one-time spreadsheet
    Access requests get handled ad hoc, with no consistent policy behind themAccess Control Engineering — least-privilege policy enforced at the database, not documented in a wiki

    Decisions We Help You Get Right

    Securing production data comes with its own set of tradeoffs. Here's how we think through the ones that come up most.

    Database-native controls vs. an enterprise governance platform

    Collibra, Immuta, and BigID carry a significant annual license cost, and the most common failure mode is paying for the platform and never configuring the workflows that make it useful. Postgres row-level security, masking views, and Vault-managed credentials solve the same problem for most teams at a fraction of the cost. We size the decision to your actual data footprint, not the vendor's pitch deck.

    Which framework to satisfy first, when more than one applies

    SOC 2, HIPAA, and PCI-DSS overlap on access control, encryption, and audit logging by a wide margin: the differences are in scope and retention period, not the underlying engineering. We sequence around whichever audit date or regulatory deadline is actually on your calendar, and the overlap means the second framework costs far less than the first.

    Encrypt everything vs. targeted field-level encryption

    Blanket application-layer encryption on every column sounds safer but adds query complexity, breaks indexing on encrypted fields, and slows down every read. Targeting the specific columns that hold regulated data (SSNs, PHI fields, payment card numbers) gets the same compliance outcome without rewriting your entire data access layer.

    We implement the controls vs. your team executes our design

    Some clients want the exposure assessment and control design, then implement it with their own engineers. Others want us to build the row-level security policies and encryption directly, especially against an audit deadline. Both are normal outcomes of the same engagement. The design doesn't change based on who writes the migration.

    Why Engineer the Control Before You Buy the Platform

    Engineering, Not Paperwork

    We implement row-level security, column masking, encryption, and audit logging directly in your database and data stack, not a policy binder that sits next to a catalog tool nobody updates.

    Built to Survive the Audit You Actually Have

    SOC 2, HIPAA, PCI-DSS, or a customer's security questionnaire: we map each requirement to the specific system it governs, so gathering evidence is a query, not a scramble.

    Sized to Your Real Exposure

    Most companies don't need a costly enterprise governance platform. We'll tell you when a database-native control (Postgres RLS, a masking view, Vault-managed credentials) solves it instead.

    Frameworks We Map to Technical Controls

    Tell us which framework you're working toward. These are the specific engineering requirements each one actually tests, not the compliance-101 version.

    SOC 2 (Type I/II)
    Access control evidence tied to specific roles, audit logging retained across the observation window, encryption in transit and at rest, and change-management logs for every schema or permission change: the controls an auditor samples directly.
    HIPAA
    PHI encryption at rest and in transit, "minimum necessary" access enforced through RBAC and row-level security rather than a policy document, audit controls under §164.312(b), and a 6-year audit log retention requirement.
    GDPR / CCPA / CPRA
    A right-to-erasure pipeline that actually reaches the primary database, replicas, backups, and caches (not just the row in the main table), plus data minimization at the schema level and consent-linked access controls.
    PCI-DSS
    Cardholder data environment scoping, PAN tokenization or masking so raw card numbers don't sit in plaintext, encryption key management with rotation, and access logging on every query that touches the CDE.

    Four Parts of Every Data Governance & Security Engagement

    Sensitive Data Discovery & Classification

    Scan production databases and warehouses to find where PII, PHI, or PCI data actually lives, not where you assume it lives, tag it, and wire that classification into access policy, not a one-time spreadsheet.

    Access Control Engineering

    Row-level security in Postgres or Snowflake row access policies, column-level masking and tokenization, and RBAC/ABAC redesigned around least privilege, enforced at the database, not documented in a wiki.

    Encryption & Secrets Overhaul

    Field-level encryption for the columns that need it, KMS-backed key management, and dynamic, short-lived database credentials via Vault or your cloud provider's secrets manager instead of static passwords in an env file.

    Audit Logging, Retention & Deletion Engineering

    Database activity monitoring and audit trails that actually answer who accessed what and when, plus a real retention and right-to-erasure pipeline that reaches primary databases, replicas, backups, and caches.

    Specific Situations This Solves

    First enterprise deal, first security questionnaire

    A Series A/B SaaS company closes its first large customer, and the questionnaire asks for row-level access control and audit logging that don't exist yet.

    SOC 2 Type II renewal with drifted controls

    Controls passed Type I a year ago; grants have accumulated since, and nobody's re-reviewed who can touch what.

    HIPAA gap before a health-data partnership

    A platform is adding PHI for the first time and needs encryption, access control, and a 6-year audit log retention path before data starts flowing.

    PCI-DSS scoping for a new payments feature

    Card data is about to enter the database, and the cardholder data environment needs tokenization and access logging before launch.

    A governance platform license sitting unused

    Collibra, Immuta, or BigID was purchased for a compliance push, and the workflows were never configured, so the license renews without solving anything.

    A deletion request that didn't actually delete anything

    A right-to-erasure request cleared the primary table but left the row in a replica, a backup, or a cache, surfaced by an audit or a customer complaint.

    What Happens After You Reach Out

    1. Diagnose
    2. Prioritize
    3. Fix
    4. Stay

    Exposure & compliance-gap assessment

    An audit of where sensitive data actually lives, who can access it, what's encrypted, what's logged, and which specific control gaps block your target framework.

    Control design

    We map each compliance requirement to a specific technical control (an RLS policy, a masking view, a KMS key, an audit table), scoped to your actual stack, not a generic framework binder.

    Pilot implementation

    We build and ship the highest-risk control first, usually access control or encryption, so you have something an auditor or customer security team can verify, not a roadmap.

    Evidence & documentation

    We package the audit logs, access policies, and encryption configuration as auditor-ready evidence, and train your team to maintain it day to day.

    Ongoing monitoring & support

    On retainer, we run continuous drift detection (a new unencrypted column, a newly over-broad grant) so the control set doesn't quietly rot between audits.

    Before → After

    The same four areas, measured before and after the engagement.

    Data governance and security control state before and after a DharmOps engagement
    AreaBeforeAfter
    DiscoverySensitive data classified once in a spreadsheet, never re-scanned as schemas changeClassification wired into access policy, re-checked as schemas evolve
    Access controlPermissions granted ad hoc, rarely revokedLeast privilege enforced as a database grant (RLS, masking), not a policy sentence
    Encryption & secretsStatic database passwords in an env fileKMS-backed field encryption and short-lived credentials via Vault or a cloud secrets manager
    Audit & retentionDeletion clears the primary table, not the replica, backup, or cacheRetention and right-to-erasure pipeline reaches every copy of the data

    In one engagement, a healthcare platform closed audit-log gaps and added continuous replication ahead of a HIPAA-covered telehealth launch.

    How This Differs From the Alternatives

    Comparison of DharmOps against alternative ways to cover data governance and security engineering
    OptionFitCost shape
    DharmOpsEngineers the control directly in your stackScoped per control area, sized to real exposure
    Enterprise governance platform (Collibra, Immuta, BigID)Strong once workflows are configured and maintainedSignificant annual license, plus the implementation work most teams underbudget
    Fractional CISOSets the security program and risk postureAdvisory, doesn't write the RLS policy or encryption config itself
    Full-time database security hireGood fit once control work is continuous, not project-shapedFull-time salary and benefits for often project-shaped work

    Frequently Asked Questions

    No. Platform engineering builds the self-service golden path for shipping pipelines. This builds the access control, encryption, and audit controls that make sensitive data safe to self-serve in the first place. They're often paired, not substitutes.

    A few patterns show up repeatedly: nobody can say with confidence which columns hold PII or PHI without checking manually, database credentials are static passwords sitting in an env file instead of short-lived Vault-issued ones, permissions get granted for a project and never revoked afterward, and a right-to-erasure or deletion request clears the primary table but not the replica, backup, or cache. Any one of these is enough to fail a SOC 2 or HIPAA control test.

    Probably not yet. If you have no regulated data and no enterprise customer sending you a security questionnaire, a full engagement is premature. Start with a lightweight access-control review instead of buying a platform you can't yet operationalize.

    In PostgreSQL, row-level security is a policy attached to a table (CREATE POLICY) that the database enforces on every query, not something the application layer has to remember to filter for. Snowflake and Databricks use row access policies to the same end. The engineering work is less the CREATE POLICY statement and more the tenant or role model behind it: which column or claim determines what a given role can see, and testing that the policy actually blocks access instead of just returning fewer rows by accident.

    Scan the actual schema and sample data, not just column names — a column called notes or metadata regularly holds PII that a name-based scan misses. We tag what we find (PII, PHI, PCI, or none) against the schema, then wire that classification into access policy and masking rules so it's enforced, not just documented in a spreadsheet that goes stale the next time someone adds a column.

    Database-level audit logging (pgAudit on PostgreSQL, or the equivalent on your warehouse) that records who accessed what, when, and through which role, retained for the window the framework requires. An auditor samples this directly, so the log needs to answer the question without someone reconstructing it by hand from application logs. HIPAA specifically requires this under audit controls (§164.312(b)) with a 6-year retention period.

    Map every place a row can end up first: the primary table, read replicas, backups, caches, and any downstream warehouse or analytics copy. A deletion pipeline that only clears the primary table is the most common gap we find — it passes casual review but fails the first time a customer or auditor asks for proof. Backups usually can't be selectively edited, so the real fix is a retention policy that ages backups out on a schedule short enough to satisfy the erasure requirement, paired with an explicit propagation step for replicas, caches, and warehouse copies.

    Usually not. Enterprise catalogs and policy engines carry a significant annual license cost, and the most common failure mode is paying for the platform and never configuring the workflows that make it useful. We often solve the same problem with database-native controls (Postgres row-level security, masking views, Vault-managed credentials) at a fraction of the cost, and only recommend a platform once you've outgrown that.

    We build and document the technical controls a SOC 2 audit actually tests: access control, encryption, audit logging, retention. We're not your auditor or your compliance-automation platform; tools like Vanta or Drata handle evidence collection. We're the engineering work those tools assume is already done.

    A fractional CISO advises on security program and risk. We're the engineers who implement the specific database and data-layer controls that program requires. Often used together: the CISO sets the requirement, we build it.

    The exposure and compliance-gap assessment is priced after a short intake call once we know your framework and data footprint. Implementation is priced per control area (access control, encryption, audit logging), and ongoing drift monitoring runs on a monthly retainer. We size the number to your actual exposure, not a one-size license fee.

    A dedicated database security or governance engineer is a significant full-time salary commitment, and most companies don't have enough ongoing control work to justify a full-time hire. We deliver the assessment and control implementation as a scoped engagement, document runbooks your existing engineers can use, then stay on a retainer to watch for drift instead of a full-time hire.

    Data governance services define who owns each dataset, who can access it, how it is classified, and how long it is kept, then build those rules into the systems that hold the data. That covers policy design, sensitive data discovery and classification, access control, audit logging, and retention and deletion pipelines. At DharmOps, the focus is the engineering that enforces the policy in your databases and warehouses, not a policy document that sits in a shared drive.

    It starts with an assessment of where sensitive data lives, who can reach it, and which controls are missing against your framework (SOC 2, HIPAA, GDPR, or PCI-DSS). From there we implement the gaps by control area: classification, row-level and column-level access, encryption and secrets, and audit and retention. You get the working controls plus documentation and runbooks your engineers can maintain.

    A data governance framework is the set of roles, policies, and controls that decide how data is owned, classified, accessed, and retired. Most frameworks stall at the policy stage. We implement one by turning each policy into something the database enforces: a classification tag that drives a masking rule, a role that maps to a row access policy, a retention rule that runs as a scheduled job.

    Governance decides the rules: who owns the data, what counts as sensitive, and who should have access. Security enforces them with encryption, access controls, credential management, and monitoring. One without the other fails an audit. A governance policy with no enforcement is a document, and security controls with no governance leave nobody able to say why access was granted.

    Data security consulting covers the data layer specifically: database and warehouse access control, encryption at rest and in transit, key and secrets management, sensitive data discovery, and audit logging. It starts with a data security assessment that lists exposed columns, over-broad grants, and static credentials, then moves to fixing them in priority order.

    DSPM tools continuously scan your cloud data stores to find sensitive data, map who and what can access it, and flag risky configurations. The tool finds the exposure; someone still has to fix it. Our DSPM implementation work connects the findings to real changes: tightening grants, adding masking, rotating static credentials, and closing unmanaged copies of data.

    Most DLP products watch endpoints, email, and file movement. Data loss prevention for databases works at a different layer: limiting bulk export rights, masking sensitive columns for roles that don't need raw values, logging large or unusual queries, and controlling which service accounts can write data outside the environment. We implement these controls in the database and warehouse, then connect the alerts to your existing monitoring.

    The engineering side of SOC 2 is the set of technical controls an auditor samples: access control and periodic access review, encryption, audit logging, change management for schemas, and backup and retention. We build and document those controls. Evidence collection and the audit itself stay with your compliance platform and auditor, such as Vanta, Drata, or your audit firm.

    For databases and pipelines, HIPAA comes down to the Security Rule technical safeguards: access control, audit controls, integrity, transmission security, and encryption of ePHI. We find where PHI sits, restrict it with role-based access and masking, encrypt it, and set up audit logging retained for the required six years. The same work extends to any warehouse or analytics copy of that data.

    For a small number of databases, classification in the schema is enough: tag columns as PII, PHI, PCI, or none, and drive masking and access policy from those tags. Data classification software earns its cost when you have many data stores and schemas that change weekly, because manual tagging stops keeping up. We help you decide where you are on that line before you buy a tool.

    Software helps with consent records, data subject request intake, and vendor registers. It does not delete a row from a replica, a backup, or a cache. That part is engineering: mapping every copy of personal data and building the erasure and retention pipeline that reaches each one. We handle that layer so the software has something real to report on.

    AI systems add new copies and new access paths for sensitive data: training sets, embeddings in vector stores, prompt logs, and retrieval pipelines that can surface a document to a user who should not see it. Governing them means classifying what goes in, enforcing the same access rules at retrieval time, and logging what the model was given. The controls are the same ones applied to a new set of data stores.

    Data Governance & Security Use Cases by Industry

    Each regulation tests a different set of controls. We build the controls the audit checks, mapped to the framework that applies to you.

    Data Governance & Security for Healthcare

    HIPAA requires that only authorized staff see patient data and that access is logged. We classify PHI, apply row-level security and masking, and keep the audit trail.

    Data Governance & Security for FinTech

    PCI DSS 4.0 expects automated controls that alert on unexpected data flows. We limit cardholder data access to need-to-know and add monitoring for movement outside approved paths.

    Data Governance & Security for Banking & Insurance

    Examiners ask who accessed what and when. We build access certification, encryption with key management, and retention rules that produce that evidence from logs.

    Data Governance & Security for SaaS & Software

    SOC 2 reviews turn on tenant isolation and access control. We enforce them in the database layer and generate the access and change evidence the auditor requests.

    Data Governance & Security for Retail & eCommerce

    GDPR and CCPA deletion requests span the warehouse, backups, and downstream copies. We build the discovery and deletion pipeline so a request is honored everywhere.

    Data Governance & Security for Enterprise Businesses

    AI and analytics tools now reach data that was never classified. We extend access policies and audit logging to those tools before they connect to sensitive tables.

    Find Out What an Auditor Would Actually Find

    Tell us which framework you're working toward (SOC 2, HIPAA, PCI-DSS, GDPR) or what a customer's security questionnaire just asked you, and we'll tell you honestly which controls are missing and which ones you already have covered.

    A Checklist Doesn't Build the Encryption

    Most teams that come to us already have the compliance framework mapped out. What's missing is the row-level security policy, the encryption, and the deletion pipeline the framework assumes exists. We build those.