Security and trust
Separation you can rely on, enforced where the data lives.
This page describes how StrikeWard works today. Items still in development are labelled as planned.
Every request is checked before data is returned.
Each record belongs to exactly one organisation. The database verifies that the signed-in user is a member of that organisation on every read and write. The organisation chosen in the browser is never trusted on its own.
Signed-in user
Identity verified on every request
Membership check
Is this user a member of the organisation?
Role check
Owner · Admin · Analyst · Viewer
Plan entitlement
Is the module included in this organisation's plan?
Four roles, applied consistently.
Roles are stored separately from user profiles and checked on the server. A user's role in one organisation has no effect in another.
Owner
- Everything an Admin can do
- Grant the Admin role
- Cannot be removed by others
Admin
- Invite Analysts and Viewers
- Change roles and remove members
- Read the audit log
Security Analyst
- Create and update findings
- Comment and assign owners
Read-Only Viewer
- View records in the organisation
- No edits, no comments
Changes leave a record.
Organisation creation, invitations, role changes and member removals are written to an audit log that owners and admins can read but nobody can edit from the app. Finding changes and comments are kept in a per-finding history written by the database itself.
organisation.createdOwnerinvitation.createdAdmin · analyst roleinvitation.acceptedNew membermember.role_changedanalyst → viewermember.removedAdmin
What your plan includes is checked on the server.
Module access is calculated from your organisation's subscription and any add-ons — never from settings in the browser. Entitlements are kept separate from roles: a valid plan never grants extra permissions, and an expired plan never opens access to another organisation.
Three independent checks. All must pass. If a plan is downgraded, existing evidence and incident history are retained rather than deleted.
Implemented today, and what's planned.
Implemented
- Database-enforced organisation isolation
- Owner, Admin, Analyst and Viewer roles
- Two-factor sign-in, which owners can require for admins
- Encryption in transit (HTTPS) for every request
- Private evidence storage with short-lived links
- Hashed, single-use, expiring links for policy and vendor requests
- Audit log for membership and security changes
- Append-only finding and incident history
- Server-checked plan entitlements
Planned
- Self-serve data export and deletion
- Automated tenant-isolation regression tests
- Independent third-party penetration test
- Single sign-on (SAML)
StrikeWard does not currently hold ISO 27001 certification or SOC 2 attestation, and no third-party penetration test results are published. StrikeWard provides security guidance and tooling; it does not guarantee protection from any breach.
If something goes wrong.
We have a written plan for handling incidents. We contain the issue, look into what happened, fix it, and tell affected customers without unnecessary delay. Where a breach is likely to cause serious harm, we notify the people affected and the OAIC under the Notifiable Data Breaches scheme.