Access scoped. Data minimised.
Review the access and data-handling requirements before an engagement begins. Audit access, evidence exports and any portal or administration service each need a clear scope, retention policy and owner.
Read-only audit access
Audit analysis does not change your configuration. Portal development and supervised administration are separate services with separately agreed permissions and approval requirements.
Least-privilege access you grant and revoke
Access is scoped to the platform and engagement: an appropriate Salesforce integration identity, a scoped HubSpot connection, or an AWS read-only role. Agree the permissions, duration and revocation process before access is granted.
Data minimisation by design
Start with licence assignments, user status and login evidence. If a finding needs record-activity metadata, agree that additional scope explicitly. Document which fields are collected and how evidence exports and operational logs are handled.
Pass-through portal architecture
A portal can use your CRM as the system of record. Its design must separately define API permissions, caching, logs, backups and retention; revoking API access does not itself delete earlier exports or logs.
Tenant isolation and audit trail
Each engagement is scoped to its own tenant boundary, and material conclusions carry a trail back to the evidence and source they rest on — which is what makes a finding reviewable rather than merely asserted.
Independent by structure
No vendor commission, no reseller margin, no referral fee. Nobody on the other side of your negotiation has a commercial relationship with us.
Security one-pager for your procurement team
Request the architecture, access scope, retention terms and sub-processor details relevant to your proposed engagement.
Trust is the product
Stage 00 is a 30-minute qualifying call at no cost. If the timing or the estate does not justify an engagement, we say so on that call.