1. compliance
prorm
  • prorm documentation
  • Known test gaps
  • Architecture
  • Core concepts
  • Database types & coverage
  • Getting started
  • Going further
  • compliance
    • Compliance
    • The security toolkit: `prorm audit`
    • Checklists by regulation
    • Declaring personal data
    • Evidence bundles
    • Evidence
    • Frameworks: `@Security`
    • Jurisdictions
    • Platform policies
    • Protecting data
    • The regulation dataset
    • Residency and cross-border transfers
    • Retention & integrity
    • Status
    • Subject rights
  • decorators
    • prorm with decorators
    • Models with decorators
    • Querying a decorated model
    • Relations with decorators
  • diagrams
    • Diagram generators
    • Chen diagram
    • Class diagram
    • Dependency diagram
    • ER diagram
    • Flow diagram
    • From your models to a diagram
    • Gantt diagram
    • Index diagram
    • Migration diagram
    • Model diagram
    • Package diagram
    • Crow’s-foot diagram
    • Schema documentation
    • Sequence diagram
    • State diagram
    • Tree diagram
  • dialects
    • SQL dialects
    • AlloyDB Dialect
    • AlloyDB Omni Dialect
    • Amazon Athena Dialect
    • Aurora DSQL Dialect
    • Amazon Aurora MySQL Dialect
    • Amazon Aurora PostgreSQL Dialect
    • Azure Database for MySQL Dialect
    • Azure Database for PostgreSQL Dialect
    • Azure SQL Database Dialect
    • Azure SQL Managed Instance Dialect
    • Google BigQuery Dialect
    • Citus Dialect
    • ClickHouse dialect
    • Cloud Authentication (`cloud-auth`)
    • Cloud SQL for SQL Server Dialect
    • Cloud SQL for MySQL Dialect
    • Cloud SQL for PostgreSQL Dialect
    • CockroachDB Dialect
    • Azure Cosmos DB for PostgreSQL Dialect
    • CrateDB Dialect
    • Cloudflare D1 Dialect
    • Databricks dialect
    • IBM Db2 Dialect
    • Dolt Dialect
    • Apache Doris Dialect
    • Druid Dialect
    • DuckDB Dialect
    • Exasol dialect
    • Microsoft Fabric Data Warehouse Dialect
    • Firebird Dialect
    • Greenplum Dialect
    • SAP HANA Dialect
    • MySQL HeatWave Dialect
    • Azure Data Explorer (Kusto) Dialect — T-SQL
    • MariaDB Dialect
    • Materialize Dialect
    • MonetDB Dialect
    • MotherDuck Dialect
    • Microsoft SQL Server Dialect
    • MySQL Dialect
    • Neon Dialect
    • OceanBase Dialect
    • openGauss Dialect
    • Oracle Dialect
    • Oracle Autonomous Database Dialect
    • ParadeDB Dialect
    • PolarDB Dialect
    • PostgreSQL Dialect
    • Presto Dialect
    • QuestDB Dialect
    • Aurora RDS Data API Dialect (`rdsdata`)
    • Amazon RDS for Db2 Dialect
    • Amazon RDS for MariaDB Dialect
    • Amazon RDS for SQL Server Dialect
    • Amazon RDS for MySQL Dialect
    • Amazon RDS for Oracle Dialect
    • Amazon RDS for PostgreSQL Dialect
    • Amazon Redshift
    • Amazon Redshift Data API Dialect
    • RisingWave Dialect
    • rqlite Dialect
    • SingleStore Dialect
    • Snowflake Dialect
    • Google Cloud Spanner Dialect
    • Spanner (PostgreSQL interface) Dialect
    • SQLite Dialect
    • StarRocks Dialect
    • Supabase Dialect
    • Azure Synapse Analytics (dedicated SQL pool)
    • Teradata Dialect
    • TiDB Dialect
    • TimescaleDB Dialect
    • Trino Dialect
    • Turso / libSQL Dialect
    • Vertica dialect
    • Vitess Dialect
    • Yellowbrick Dialect
    • YugabyteDB Dialect
  • guides
    • Access rules and behaviour profiles
    • ArangoDB (AQL)
    • Associations
    • Audit levels and escalation
    • Audit logging
    • In the browser
    • Bulk operations
    • Caching
    • Capabilities, tiers and team roles
    • CLI
    • Cloudflare
    • Compliance & data protection
    • Connection Pooling & Performance
    • Security in the console
    • Couchbase: structured N1QL queries
    • Data types
    • Decorators
    • Eager loading
    • Enums and constants
    • Error handling & error types
    • Extensions
    • External fields
    • Foreign data wrappers
    • Graph databases
    • Hooks & lifecycle events
    • Indexes & constraints
    • InfluxDB: structured Flux pipelines
    • klock-errors
    • klock — the `.klock` file
    • Local databases (`prorm db up`)
    • Structured log search — Splunk, Graylog, Papertrail, Sumo Logic
    • Logging
    • Grafana Loki: structured LogQL queries
    • MCP server
    • Migrate — the data transfer subsystem
    • Migrations & Schema Sync
    • Models from an existing database
    • Defining models
    • Multiple databases
    • OrientDB, Neptune and TigerGraph
    • Passwords
    • Importing a Prisma schema
    • Structured PromQL and MetricsQL
    • Query firewall
    • QueryInterface
    • Query operators reference
    • Query optimization
    • Composing find options with `pipe()` and `Q`
    • Query safety: the fail-closed WHERE guard
    • Querying
    • Raw Queries & Query Building
    • Read replicas
    • Schema diffing & migration generation
    • Views, triggers & other schema objects
    • Scopes & default scopes
    • Seeders
    • SPARQL / RDF triplestores
    • SQL constants
    • SQL features
    • SQL function builders
    • SQLite advanced features
    • StoreKey — a prod-orm database as the storage
    • Streaming results
    • Terraform
    • Transactions & Isolation Levels
    • Type mapping: legacy and modern
    • TypeScript types
    • Database users, roles & privileges
    • Validation & constraints
    • Virtual & Computed Fields
    • Writing docs
  • javascript
    • prorm in JavaScript
    • Models in JavaScript
    • Querying in JavaScript
    • Relations in JavaScript
  • runbooks
    • Operational runbooks
    • Connection failures
    • Credential rotation
    • Failover
    • Incident checklist
    • Deploying klock v2
    • Migration rollback
  • running-databases
    • Running databases in Docker
    • Running prorm under Bun in Docker
    • Running Cassandra in Docker with prorm
    • Running ClickHouse in Docker with prorm
    • Running CockroachDB in Docker with prorm
    • Running prorm under Deno in Docker
    • Running Elasticsearch in Docker with prorm
    • Running MariaDB in Docker with prorm
    • Running MongoDB in Docker with prorm
  • prorm control plane
    • Introduction
    • Authentication
    • Errors
    • Getting started
      • Service
        • Is it up
        • This description
    • Account
      • Sign-up and verification
        • Create an account
        • Exchange credentials for a token
        • Verify with the emailed code
        • Verify by clicking the emailed link
        • Name the parent or guardian
        • What a consent link is about
        • Give consent for a child's account
        • Ask the parent or guardian again
        • Send a new code and link
      • Family
        • Everyone this account is responsible for
        • One child, in detail
        • Turn a limit on or off
      • Profile
        • Who am I
        • Change the account
        • Every address on the account
        • Add an address
        • Confirm an address with the code mailed to it
        • Mail a fresh code to an unconfirmed address
        • Make an address primary
        • Remove an address
        • What this caller may do
    • Security
      • Sessions
        • Everywhere this account is signed in
        • Sign out everywhere else
        • Sign one out
        • A token for the CLI on a named machine
        • A token for the customer console, from the staff one
        • Park a sign-in for the CLI to collect
        • The CLI collecting its sign-in
        • The team's members' live sessions
        • Sign a member's session out
        • Sign an account out everywhere
        • Everywhere the account is signed in
        • Sign an account's session out
      • Single sign-on
        • Begin a single sign-on
        • The provider's return
        • Link the signed-in account to a team's provider
        • Which team an address signs in to
        • The team's single sign-on, as a member sees it
        • Set the team's OpenID Connect provider up, or change it
        • Remove the provider
        • The team's domain claims and the DNS record each needs
        • Prove a claimed domain
      • MFA and passwords
        • Start enrolling a second factor
        • Prove the app has it
        • Remove the second factor
        • Ask for a reset link
        • Set a new password with the emailed token
      • Klock
        • Open a device-bound klock session
        • Check in, for the next grant
        • Step up the session asking
        • Rotate the device key
        • Freeze a session
        • Unfreeze a session
        • A guest grant
        • The revocation feed
        • The published keyset
        • What this control plane supports
      • Devices
        • Your devices, or a team's
        • Approve a new device's pairing code
        • One device
        • Rename a device
        • Revoke a device
        • Suspend a device
        • Reinstate a suspended device
        • Wipe a device
        • Ask a device to rotate its key
        • The team's members' devices
        • Revoke a member's device
        • An account's devices
        • Revoke an account's device
        • Wipe an account's device
        • The device fleet
      • Access rules and behaviour
        • The access rules that bear on you
        • Add an access rule
        • This request, as the rules see it
        • One access rule
        • Remove an access rule
        • The behaviour profiles that bear on you
        • Add or change a behaviour profile
        • The profile presets
        • Your behaviour findings
        • Acknowledge a finding
        • One behaviour profile
        • Remove a behaviour profile
        • The team's access rules
        • Add a team access rule
        • Remove a team access rule
        • The team's behaviour profiles
        • Add or change a team behaviour profile
        • Remove a team behaviour profile
        • What the team's profiles caught
        • Acknowledge a team finding
      • Recovery and lockdown
        • Ask for a recovery link
        • Recover access with the emailed code
        • Is the account locked down
        • Lock the account down
        • Release a lockdown
        • Lock a member down
        • Release a member's lockdown
      • MCP tokens
        • Make a delegated token for one MCP client
        • The account's delegated tokens
        • Revoke a delegated token
        • What a delegated token may do now
        • Run one MCP tool with a delegated token
        • Run a device-signed MCP tool call relayed by the MCP Worker
      • Kerberos
        • Give the team its own Kerberos realm
        • The team's realm
        • Remove the team's realm
    • Logging and monitoring
      • Audit log
        • What has been done to the account
        • What has happened to this account
        • The account's audit trail
      • Operations
        • Everything that has been asked of this database
        • One, with its steps
        • Stop it
        • Put a failed one back in the queue
        • Every operation, across all accounts
      • Metrics and events
        • Every measurement, for a graph
        • Who did what to it
    • Billing
      • Plans and pricing
        • What the plans allow
        • The rate card
        • What one database would cost
        • What this account is paying for, itemised
      • Subscriptions and invoices
        • What this month's invoice will say
        • What this account is on
        • What it has been charged
        • Start a Stripe Checkout session
        • Open the customer portal
        • Stripe's events
        • Buy more connection pools
      • Team billing
        • The team's billing account
        • What the team has been charged
        • What this month's invoice will say
        • The team's cards
        • Add a card, through a Stripe-hosted setup session
        • Make a card the team's default
        • Remove a card
        • Start the team paying
        • Open the Stripe portal on the team's customer
        • Change the team's plan
        • Who receives the team's bills
        • How the team pays for transfers
    • Support
      • Support chat
        • My conversations
        • Start a conversation
        • Every support conversation, open first
        • A ticket for the socket
        • One conversation, with who is in it and who is connected
        • Rename a group; open or close a support conversation
        • The lines, oldest first
        • Say something
        • Add somebody
        • Mark read
    • Administration
      • Users
        • Every account
        • One account, with everything hanging off it
        • Grant or revoke admin
        • Verify an account by hand
        • Lock or unlock sign-in
        • Allow or hold provisioning
        • Send the verification mail again
        • Set the plan by hand
      • Platform
        • Every database and store, across all accounts
        • The counts worth putting on a dashboard
      • Staff and permissions
        • What kind of admin the caller is, and which scopes they hold
        • The admin presets
        • Every admin, and the scopes each resolves to
        • Make an account an admin of a kind
        • Change an admin's kind, or a custom admin's scopes
        • Revoke admin
      • Team administration
        • Every team, with its owner and size
        • One team in full — members with their accounts, and projects
        • Hand the team to another member
        • Put an account in the team, active at once
        • Change a member's role
        • Remove a member
      • Assumed identities
        • Assume an identity — act as a customer account
        • The identities the caller holds open
        • End an assumed identity
      • Support inbox
        • The platform's addresses
        • Add a platform address
        • One address, with its counts
        • Change an address's label, routing, or whether it accepts mail
        • Remove an address that holds no mail
        • Make, adopt or repair the address's routing rule
        • Every admin's personal address, made where missing
        • File a raw message, as if it had arrived
        • The inbox
        • One message, whole
        • Mark a message
        • Hand a message to an admin, or take it back
        • Leave an internal note
        • Reply, from the address the message came to
        • What is waiting
    • Databases
      • Databases
        • Data stores
          • Every data store on the account
          • Provision a data store
          • Change a data store that is already running
          • One data store
          • Deprovision it
          • Report what it is using
          • How to reach a data store
        • Connections and credentials
          • The api keys on a database
          • Issue a key
          • Revoke a key
          • The engine users we created
          • Create a user inside the database
          • Give a user a new password
          • Drop a user
          • How the database is reached
          • Set how it is reached
          • Revoke every api key on it
          • How to connect to it
          • The ssh keys that open its bastion
          • Add a key, or have one made
          • The private half of a generated key, once
          • Revoke an ssh key
        • Schema and objects
          • The SQL objects we put in it
          • Create one, and apply it
          • What is in the database, as the engine reports it
          • One table
          • What it would run, without running it
          • Redefine an object in place
          • Drop it
          • The extensions installed in it
        • Migrations
          • A plan compiled to statements, recording nothing
          • The migrations recorded for it
          • Record one
          • Apply everything recorded and not yet run
          • Apply everything pending, oldest version first
        • Lifecycle
          • Grow or shrink it
          • Stop it accepting connections
          • Start it again
          • Move it to another region
        • Backups and replicas
          • Take a backup
          • The backups it has
          • Restore one into it
          • What has been restored into it, and from where
          • Its read copies
          • Add one
        • Policies
          • The catalog
          • One policy
          • What this database is held to
          • Switch a policy on, or change its knobs
          • Switch it off
          • Mark the policies reviewed
          • Evaluate the periodic policies now
          • Who is behind a credential
        • Passwordless
          • The database's passwordless sessions
          • Issue a passwordless session (v1)
          • Revoke a passwordless session
          • Bind a session to a device key
          • Issue a v2 session for a host to bind
          • Redeem an enrolment ticket on the host
          • Check a passwordless credential
          • Run one described query under a passwordless credential
        • Database roles
          • The database's roles
          • Define a role
          • One role
          • Change what a role permits
          • Delete a role, and revoke every key granted it
          • Grant a role, which mints a key
          • Who holds a role
          • The api keys bound to a role
        • Pools
          • A database's connection pools, and how busy each is
          • Open another pool
          • Rename a pool or change its size
          • Close a pool
        • Data plane
          • Run a query against a database
          • Several statements, in order, over one connection
          • Is this database answering
          • What the proxy itself is holding
        • Transfers
          • The strategies this account's tier may use
          • Price a transfer without creating it
          • The account's transfer jobs, newest first
          • Create a transfer job
          • One job, and whether its certificate holds
          • Cancel an unfinished job
          • Start a created job, confirming its price
          • Report a job's status (the runner, or the owner's side of a local run)
        • Every database on the account
        • Provision a database
        • Change a database that is already running
        • One database
        • Deprovision it
        • Read or write it
        • Report what it is using
        • The engines this API will provision
        • Where a managed database can be put
    • Teams
      • Teams
        • Members
          • Who is on it
          • Invite somebody
          • Accept an invitation
          • Change somebody's role
          • Remove somebody
        • Projects
          • The projects a team runs
          • Start one
          • Rename a project, or move its environment
          • Delete a project
          • One project, and what is in it
          • Put a database or store in it
          • What is in a project
          • Take one out
        • The teams this account is on
        • Start one
        • The twelve roles, and what each may do
        • Rename a team
        • Close a team
        • One team
        • Hand the team to somebody else
        • Leave a team
    • Schemas
      • Error
      • ValidationErrors
      • Token
      • PolicyCategory
      • PolicySeverity
      • PolicyAction
      • PolicyTrigger
      • PolicyParam
      • Policy
      • PolicyCatalog
      • PolicyAssignment
      • PolicyOutcome
      • PolicyFiring
      • CredentialTrace
      • Relation
      • Restrictions
      • ChildSummary
      • SignupRequest
      • SigninRequest
      • UpdateMeRequest
      • User
      • Address
      • GeoPoint
      • D1Region
      • Usage
      • UsageReport
      • Resource
      • Database
      • DataStore
      • NewDatabase
      • NewDataStore
      • QueryRequest
      • DatabasePrivilege
      • ApiKey
      • DbUser
      • Access
      • AccessRequest
      • DatabaseObject
      • NewDatabaseObject
      • NewMigration
      • SchemaOperation
      • Migration
      • Operation
      • Session
      • AdminPowers
      • Admin
      • AuditEntry
      • TeamRole
      • Conversation
      • ChatMessage
      • TeamSso
      • Team
      • TeamMember
      • SshKey
      • ConnectionInfo
      • InboxAddress
      • InboxMailbox
      • InboxMessageSummary
      • InboxMessage
      • InboxNote
      • Page
      • Quote
      • Plan
      • ApiError
      • CapabilityRefusal
      • KlockErrorCode
      • PageWindow
      • SessionView
      • KlockStepUpRequest
      • KlockOpenRequest
      • KlockOpenedSession
      • UpdateMeResult
      • CapabilitiesView
      • SessionLimits
      • Device
      • DeviceListed
      • DeviceTeamRef
      • DeviceCommand
      • DeviceAuditLine
      • DeviceActionRequest
      • StaffActionRequest
      • ManagedSession
      • SessionRevoked
      • AccessRule
      • AccessRuleRequest
      • BehaviourProfile
      • BehaviourProfileRequest
      • BehaviourProfileSaved
      • BehaviourFinding
      • BehaviourFindingAck
      • StepUpProof
      • Removed
      • MemberLockdownRequest
      • McpClient
      • McpDelegatedView
      • McpToolCall
      • McpForwardRequest
      • PasswordlessScope
      • RoleScope
      • PasswordlessSession
      • PasswordlessTlsMaterial
      • PasswordlessKerberosMaterial
      • ServiceDeviceKeys
      • ServiceSession
      • DatabaseRole
      • TransferEndpoint
      • TransferJobRequest
      • TransferQuote
      • TransferStrategy
      • TransferJob
      • TransferJobAccess
      • Pool
      • PoolAllowance
      • BillingSubscription
      • Invoice
      • BillingContact
      • PaymentMethod
      • UpcomingCharges
      • TeamBilling
      • TeamKerberosRealm
      • TeamSsoDomain
      • TeamSsoResponse
      • StoreConnection
      • BatchFailure
      • ProxyStatus
  1. compliance

Frameworks: `@Security`

Jurisdictions answer what may be held. Frameworks
answer the other question an auditor asks: which controls are on? SOC 2
wants an audit trail and retention; PCI DSS wants encryption, masking and
TLS; SOX wants records that cannot be altered. @Security takes the names
and switches on what each requires, alongside anything you ask for directly.
import { Security, SecurityFramework, setupSecurity, setupAllSecurity } from 'ts-prorm-orm';

@Security({
  frameworks: [SecurityFramework.GDPR, SecurityFramework.HIPAA],
  audit: true,
  encrypt: ['ssn', 'diagnosis'],
  mask: { ssn: 'ssn', email: 'email' },
  retention: { years: 7 },
  autoClassify: true,
  getUserId: () => currentUser()?.id,
  getIpAddress: () => currentRequest()?.ip,
})
class Patient extends Model { /* … */ }

setupSecurity(Patient, prorm);   // or setupAllSecurity(prorm) once every model is registered

Two steps, on purpose#

Decoration records intent and applies what can be applied to a bare class;
setupSecurity() wires the hooks that need a model attached to a Prorm
instance. Skipping the second step leaves the decorator as metadata, so
call it — or setupAllSecurity(prorm) after all models are registered.
At decorationAt setupSecurity()
classification (classify, autoClassify), lineage, session isolation, WORM, rate-limit registration, cross-border log, the __security_* flagsencryption hooks, masking hooks, the retention policy, the audit trail, immutability and versioning

The options#

interface SecurityOptions {
  frameworks?: SecurityFramework[];

  audit?: boolean;                    // ComplianceAuditTrail on every create/update/destroy
  encrypt?: string[];                 // FieldEncryption on these columns
  mask?: Record<string, 'ssn' | 'card-last4' | 'card-first6' | 'email' | 'phone' | 'full'>;
  retention?: RetentionDuration;      // DataRetentionPolicy.set(Model, { maxAge })
  immutable?: boolean;                // ImmutableRecord.makeImmutable
  versioning?: boolean;               // …and enableVersioning
  rls?: (ctx: any) => { where?: Record<string, any> };   // RowLevelSecurity.apply
  classify?: Record<string, 'PII' | 'PHI' | 'PCI' | 'FINANCIAL' | 'HEALTH' | 'BIOMETRIC'>;
  autoClassify?: boolean;             // DataClassifier.autoDiscover by column name
  lineage?: boolean;                  // @LineageTrack
  sessionIsolation?: boolean;         // @TenantIsolation — with tenantIdField (default 'tenantId')
  tenantIdField?: string;
  worm?: boolean;                     // @WORM, retention from `retention` or 7 years
  rateLimit?: boolean;                // @RateLimit registration
  breachDetection?: boolean;          // flag only — see below
  crossBorderLog?: boolean;           // CrossBorderLog.enable
  sensitiveDataDiscovery?: boolean;   // flag only
  consentVersioning?: boolean;        // flag only
  dsar?: boolean;                     // flag only
  pia?: boolean;                      // flag only
  backupVerification?: boolean;       // flag only
  queryFirewall?: boolean;            // flag only

  getUserId?: () => string | number | undefined;   // for the audit trail
  getIpAddress?: () => string | undefined;
}

What a framework actually switches on#

Each framework maps to a set of requirements. Read the table below
carefully, because the requirements fall into three kinds:
1.
Applied for you when the framework is named: audit,
classification (as autoDiscover), lineage, immutable (with
versioning), sessionIsolation, worm, rateLimit.
2.
Need a field list from you: encryption, masking, retention,
rls. A framework cannot know which columns hold the card number; naming
PCI DSS says encryption is required, and encrypt: ['cardNumber'] says
where. Name the framework without the fields and nothing is encrypted.
3.
Recorded, not wired: consent, tls, pseudonymize,
breachDetection, backupVerification, queryFirewall (and the
crossBorderLog, dsar, pia, consentVersioning,
sensitiveDataDiscovery options). These set a __security_* flag you can
read back, and nothing else — and setupSecurity() warns, once per model,
naming each one and what to call instead. Pass onUnwired: 'throw' to
refuse instead, or 'ignore' once you have wired them yourself.
securityWiring(Model) returns { wired, flagOnly }; tooling uses it so
a flag is never counted as evidence. Wire the subsystem
directly — ConsentRecord,
TLSEnforcer, PseudonymizationService,
BreachDetector, QueryFirewall.
The decorator is a checklist with the hands to tick some boxes itself. The
checklists page walks each major regulation through all
three kinds.

A PCI model, and what it leaves you to do#

PCI DSS requires audit, encryption, masking and TLS. Naming the columns
covers the first three; TLS is a property of the connection, so no model
decorator can switch it on:
import {
  Model, Security, SecurityFramework, setupSecurity, securityWiring,
  configureFieldEncryption, TLSEnforcer, Prorm,
} from 'ts-prorm-orm';

declare const prorm: Prorm;

configureFieldEncryption(process.env.FIELD_KEY!);

@Security({
  frameworks: [SecurityFramework.PCI_DSS],
  encrypt: ['cardNumber'],
  mask: { cardNumber: 'card-last4' },
  onUnwired: 'throw',            // refuse to boot with a control that nothing enforces
})
class PaymentMethod extends Model {
  declare cardNumber: string;
}

TLSEnforcer.enforce(prorm, { mode: 'strict' });   // the part PCI needs that no decorator can do

try {
  setupSecurity(PaymentMethod, prorm);
} catch (err) {
  // onUnwired: 'throw' names each gap; here, `tls (implied by a framework)`
  console.error((err as Error).message);
}

securityWiring(PaymentMethod);
// { wired: ['encryption', 'masking', 'audit'], flagOnly: ['tls'], unwired: [ … ] }
securityWiring() reads what the decorator recorded, so tls stays in
flagOnly even after TLSEnforcer.enforce(): the enforcer is attached to
the Prorm instance, not to the model. Once it runs at startup, set
onUnwired: 'ignore' on that model. With the default 'warn', the same gap
prints once:
[Security] PaymentMethod: 1 control(s) are recorded but not wired, so nothing enforces them:
  - tls (implied by a framework): nothing is wired; call TLSEnforcer.enforce(prorm) at startup and TLSEnforcer.verifyRuntime(prorm)
Set onUnwired: 'ignore' to silence this once you have wired them yourself.
[!WARNING]
Naming a framework without the field lists encrypts nothing.
frameworks: [SecurityFramework.PCI_DSS] alone records encryption and
masking as unwired, and the card number is stored in plain text.

The 61 frameworks#

SecurityFramework names them; FrameworkCategories groups them;
FrameworkRequirements is the table below; getAllFrameworks(),
isValidFramework() and getFrameworkCategory() answer questions about them.

Privacy Regulations#

FrameworkSwitches on
GDPRaudit, encryption, retention, masking, consent, RLS, pseudonymise, classification, TLS, lineage
CCPAaudit, encryption, retention, masking, consent, RLS
CPRAaudit, encryption, retention, masking, consent, RLS
PIPEDAaudit, encryption, retention, consent, RLS
LGPDaudit, encryption, retention, consent, RLS
APPIaudit, encryption, consent, RLS
PIPAaudit, encryption, consent, RLS
PIPLaudit, encryption, retention, classification, TLS
DPDPaudit, encryption, retention, consent, RLS
PDPA_Thailandaudit, encryption, consent, RLS
PDPA_Singaporeaudit, encryption, consent, RLS
PDPA_Philippinesaudit, encryption, consent, RLS
PDPA_Malaysiaaudit, encryption, consent, RLS
PDPA_Indonesiaaudit, encryption, consent, RLS
PDPA_Vietnamaudit, encryption, consent, RLS
PoPIaudit, encryption, consent, RLS
NDPRaudit, encryption, consent, RLS
KVKKaudit, encryption, consent, RLS
UK_GDPRaudit, encryption, retention, masking, consent, RLS, pseudonymise, classification, TLS

Financial Regulations#

FrameworkSwitches on
PCI_DSSaudit, encryption, masking, TLS
SOXaudit, immutable, retention, lineage, WORM
GLBAaudit, encryption, masking
MiFID_IIaudit, retention
EMIRaudit, retention
Basel_IIIaudit, retention, lineage
Dodd_Frankaudit, retention
SEC_17a_4audit, immutable, retention, WORM
FINRAaudit, retention
NYDFSaudit, encryption, TLS
DORAaudit, encryption, retention, RLS, WORM

Healthcare#

FrameworkSwitches on
HIPAAaudit, encryption, masking, RLS, classification, lineage
HITRUSTaudit, encryption, masking, RLS, classification
21_CFR_Part_11audit, immutable
EU_Annex_11audit, immutable
ALCOA+audit, immutable
GAMP_5audit, immutable
ICH_E6_GCPaudit, immutable
DISHAencryption, classification

Government / Defense#

FrameworkSwitches on
FedRAMPencryption, TLS, classification, session isolation
FISMAaudit, encryption, TLS
NIST_SP_800_53audit, encryption, RLS, classification
NIST_SP_800_171audit, encryption, RLS
NIST_CSFaudit, encryption, retention, classification, breach detection
CMMCencryption, RLS
DFARSencryption, RLS
ITARencryption, classification
CJISaudit, encryption, RLS
NERC_CIPaudit, encryption, RLS

Industry Standards#

FrameworkSwitches on
ISO_27001audit, encryption, RLS, classification
ISO_27017encryption, TLS, session isolation
ISO_27018encryption, classification
ISO_27701classification, consent
ISO_22301retention
SOC_2audit, encryption, retention
SOC_1audit, retention
CIS_Controlsaudit, encryption, breach detection, rate limit, backup verification
OWASP_Top_10encryption, masking, rate limit, query firewall

Cloud & International#

FrameworkSwitches on
CLOUD_Actencryption, classification
Schrems_IIencryption, pseudonymise
Essential_Eightencryption, RLS
IT_Grundschutzaudit, encryption, RLS

@Table and @Database#

Two more decorators carry metadata only — nothing reads them to enforce, but
the sheet and your own tooling can:
import { TableSecurity, DatabaseSecurity } from 'ts-prorm-orm';

@DatabaseSecurity({
  name: 'clinical',
  region: 'eu-west-1',
  requireTLS: true,
  defaultClassification: 'CONFIDENTIAL',
  defaultAudit: true,
  defaultRetention: { years: 7 },
  allowedCountries: ['DE', 'FR'],
})
class ClinicalDatabase {}

@TableSecurity({ schema: 'phi', classification: 'SECRET', rlsEnabled: true, auditEnabled: true, dependsOn: ['patients'] })
@Security({ frameworks: [SecurityFramework.HIPAA] })
class Encounter extends Model { /* … */ }
Two name clashes to know about. At the package root, Table is the
model decorator (tableName, timestamps, …) and Database is the
collation decorator. The compliance pair are exported from the root as
TableSecurity and DatabaseSecurity, and under their own names
from 'ts-prorm-orm/compliance'.

Reading it back#

import {
  getSecurityFrameworks, getTableSecurity, getDatabaseSecurity, hasAudit, isImmutableModel,
} from 'ts-prorm-orm';

getSecurityFrameworks(Patient);   // ['GDPR', 'HIPAA']
hasAudit(Patient);                // true
isImmutableModel(LedgerEntry);    // true
getTableSecurity(Encounter);      // { schema: 'phi', classification: 'SECRET', … }
getDatabaseSecurity(ClinicalDatabase);
Next: Protecting data — the controls themselves.
Modified at 2026-10-04 00:40:16
Previous
Evidence
Next
Jurisdictions
Built with