Data residency
Australian regions first. The founding cohort is Australian regulated entities, so the platform is deployed into Australian infrastructure rather than treating residency as a later enterprise upgrade. Where a workload must remain onshore, that is the default rather than a configuration exception.
Residency comes up early in most Australian vendor reviews, and is frequently where cross-border SaaS fails the first gate. It is worth being precise with your reviewer about three separate questions that often get collapsed into one: where data is stored, where it is processed, and where support staff can access it. All three get asked, and we answer all three in writing during onboarding.
Encryption and key management
- Encryption in transit and at rest across the platform.
- Per-organisation key management. Keys are scoped to your organisation rather than shared across tenants, so cryptographic separation follows the same boundary as the trust model.
- Rotation. Keys are rotated, and an attestation can be re-anchored to a new key without re-verifying the legal entity from scratch.
Per-organisation keys matter more here than in ordinary multi-tenant SaaS. The platform's entire function is to assert who a party is; if key material were pooled across tenants, that assertion would be weaker than the thing it is asserting.
Revocation
Any party, or any individual scope, can be revoked instantly, and the effect is network-wide. Because counterparties check attestation centrally at exchange time rather than holding a secret they were issued once, withdrawal does not depend on every counterparty noticing and acting.
A useful question to put to any agent vendor: how long does it take to sever a compromised external dependency, and whose cooperation is required for it to take effect? The gap between “we can disable the integration our end” and “the counterparty loses access everywhere, immediately” is the one that matters during an incident.
Minimisation and zero-retention
Schema-negotiated exchange means the boundary can enforce what a counterparty actually needs, rather than passing whatever the source system happens to hold. Redaction and minimisation are applied at the boundary, so a confirm-only answer — “yes, twelve of twelve months, within the stated range” — can replace transferring the underlying record at all.
Zero-retention mode can be configured for nominated sensitive data classes: the attestation, the policy decision and the outcome are sealed to the audit ledger, while the payload itself is never persisted. You keep provable evidence that a permitted exchange occurred, without keeping the material that made it sensitive in the first place.
Controls roadmap
MCPLayer's controls are aligned to SOC 2 and ISO 27001 — a roadmap, not a current certification. This is a pre-launch platform onboarding a founding cohort, and claiming otherwise would fail the first question of any serious review. Ask us for current status in writing and you will get a dated answer.
What that means practically for a founding member: controls are designed against those frameworks from the start rather than reverse-engineered later, and founding members see the certification timeline and supporting evidence as it develops. If your procurement process has a hard certification gate before contract, say so at the first conversation rather than the fifth — it is a legitimate constraint and we would rather plan around it than discover it late.
Disclosure and contact
Security issues should be reported to the team directly through the contact form, marked for security. We will acknowledge them, and we will not pursue researchers who report in good faith and allow reasonable time to remediate.
For a full questionnaire response, architecture documentation or a security review call, the fastest route is to apply for the founding cohort and say that security review is your first requirement.
Are you SOC 2 or ISO 27001 certified?
Not yet. Controls are designed in alignment with both, and certification is on the roadmap. We would rather tell you that directly than have you find it during due diligence.
Where is our data stored?
Australian regions first. Storage, processing and support-access locations are confirmed in writing for your specific configuration during onboarding.
Can we run zero-retention for sensitive classes?
Yes, configured per data class. The exchange is still attested, policy-checked and sealed to the ledger; the payload is not persisted. This is usually the right setting for anything you would not want to hold a copy of.
How does this map to APRA CPS 234?
CPS 234 expects information security capability commensurate with the threat, and testable control effectiveness. The relevant controls are counterparty identity, scoped access, attribution and revocation — mapped in detail on APRA CPS 230 and AI agents.