Trust around engagement dossiers
PSM records operationally what was agreed, changed and executed per engagement. Organisations with heavier requirements can align extra access, export and audit features.
Context: demonstrability & data
Where organisations ask for more demonstrable organisation of engagements, a dossier that records facts becomes more relevant. PSM supports that record-keeping as a dossier layer — without legal conclusions or an automatic compliance outcome.
The platform is designed around a minimal data model (minimum data model): no special categories of personal data are required for core functionality.
Audit trail & timestamps
Confirmations are timestamped and retrievable. The dossier is exportable as a dossier layer.
Exportable dossier
PDF is standard for operational handover. JSON snapshot is intended for organisation roles. CSV and bundle are intended for internal review and handover via Trust Pack.
Trust Pack JSON package and bundle include a dossier fingerprint (hash) and a verify-chain endpoint for signed-in users with project access under Trust Pack. PDF is a handover export, not a public verification link.
Organisation separation & access
Multi-organisation setup with separation per organisation and access control (in line with your configuration).
Integration security (pilot)
In integration scope we work with partner/organisation keys and controlled webhook/API communication — aligned per pilot.
This falls under Integrations Pack, not Security Add-on.
Trust Controls
Available via Security Add-on where activated
PSM keeps the data model minimal, with concrete access controls for organisations that want extra certainty.
- SSO on request for pre-provisioned accounts: OIDC/SAML per organisation where configured (for example Okta or Microsoft Entra); no automatic user creation from the IdP response.
- 2FA policy setting per organisation
- IP allowlisting (access via office/VPN)
- Session management (maximum session duration)
Audit en gecontroleerde toegang
Beheerexport en advanced audit export-scope op projectniveau
- Filter by entity, action, actor and period (internal admin export)
- JSON or CSV export via the admin interface for internal reviews and investigation
- Advanced audit export with SIEM-ready mapping at project level (Trust Pack + advanced audit export + organisation-side roles with project access — same threshold as export-pack): JSON mapping for pull-oriented consumption of export-pack data; PSM does not push live security monitoring into your environment.
- External links for view-only or audit-only receipt acknowledgement, issued by authorised organisation roles with project access
- Intended for internal reviews, investigation and client audits
Security Control Matrix
Security Control Register
Per control: scope, evidence route and activation conditions.
Document Class
PSM Security Control Register
| Control ID | Domain | Control | Scope / Pack | Evidence route | Activation status |
|---|---|---|---|---|---|
| PSM-AT-01 | Audit | Audit trail & timestamps | Core | Dossier events and PDF export show event rules and timestamps. | Available in Core |
| PSM-ID-02 | Identity | SSO on request (OIDC/SAML where configured) | Security Add-on | Login flow with SSO policy active, without local password path. | Requires Security Add-on |
| PSM-ID-03 | Identity | 2FA policy per organisation | Security Add-on | Policy active: magic-link login is blocked, user is directed to SSO (MFA at IdP level). | Requires Security Add-on |
| PSM-NA-04 | Network Access | IP allowlisting | Security Add-on | Allowlist configuration active: magic-link request from unauthorised IP is blocked. Applies at authentication, not for existing sessions. | Requires Security Add-on |
| PSM-SE-05 | Session | Session management | Security Add-on | Configured session max age is applied when creating a PSM session (OIDC/SAML flows). Supabase magic-link session respects the shorter of policy and Supabase default. | Requires Security Add-on |
| PSM-AE-06 | Audit Export | Advanced audit export | Security Add-on | Admin export with actor/period filter and JSON/CSV output file, where audit export is activated. | Where audit export is activated |
| PSM-SI-07 | Audit export | SIEM-ready mapping endpoint | Trust Pack + Advanced audit export | Endpoint response at project level with Trust Pack + advanced audit export active; organisation-side roles with project access only (same threshold as export-pack). Pull-oriented schema — not a live SOC feed. | Requires Trust Pack + advanced audit export |
| PSM-IN-08 | Integrations | Integration authentication (keys/webhooks) | Integrations Pack | Signed webhook/API key flow on active Integrations Pack. | Requires Integrations Pack |
Security/identity controls fall under Security Add-on. Integration connections fall under Integrations Pack. This keeps scope and contracting boundaries clear.
Security & Trust
Audit trail & export
Changes and confirmations are recorded with timestamps so you can retrieve per engagement what was agreed. Export is intended as an evidence layer (substantiation of recording), not as a legal statement.
Access & separation
Access is role-based. In a multi-organisation context, the setup is intended to limit access to organisation data within configured tenant and role boundaries.