IAMCastle security
Security and evidence integrity
IAMCastle is designed to collect useful Microsoft Entra ID evidence without taking control of the customer tenant. These are the foundations behind that approach.
Read-only Microsoft Graph
IAMCastle requests the directory, application, policy, and audit-log read permissions needed to collect evidence. It does not request permission to change customer tenants.
Microsoft SSO
Customer users authenticate with their own organisation identities. IAMCastle does not create or retain customer passwords.
Tenant isolation
Customer identity, evidence, exports, settings, and administrative actions are authorised and scoped to the resolved customer tenant before data is returned.
Tamper-evident records
Each canonical evidence payload receives a SHA-256 fingerprint and a link to the previous record hash, allowing missing or altered retained evidence to be detected.
Protected transport and storage
Confidentiality is handled separately from hashing through TLS, protected cloud storage, access controls, and restricted platform administration.
UK data residency
The standard production deployment stores customer data in the UK. EU and US region options are available by arrangement through hello@iamcastle.io.
Why the SHA-256 hash matters
A hash is a repeatable digital fingerprint of an evidence record. Changing even one actor, timestamp, object, or old and new value produces a different result. Linking each fingerprint to the one before it makes silent editing or removal detectable when the chain is verified.
Hashing proves integrity; it is not encryption. IAMCastle uses separate controls to protect the confidentiality of the underlying data.