Engagement boundaries
Access should follow the work.
A readiness review needs evidence, not unrestricted control of your account. Before work starts, we agree the access scope, data handling and end-of-engagement cleanup with your team.
Read-only, scoped, revocable
Your account stays yours
Use a customer-approved IAM role with temporary credentials. Agree the required read actions and Kubernetes permissions for the selected clusters; read-only should not silently include unrestricted secret access.
You approve the boundary
Review the role policy and trust relationship before granting access. Production writes require a separate implementation scope. The readiness review does not modify workloads or infrastructure.
Revoke when work ends
Your team can remove the trust relationship or role. Agree an access expiry and confirm revocation at handover. Keep account audit logging under your control.
Collect the evidence you need
The review should use configuration and operational evidence relevant to the agreed questions. Redact credentials, application secrets, personal data and customer payloads before sharing exports or logs. If sensitive evidence is unavoidable, agree a secure transfer method and handling rules before sending it.
We document what was observed and what could not be checked. Reports should reference findings without reproducing secret values. The form on this site is for initial contact, not credentials or production logs.
AI tools and your data
Customer configuration, logs or reports must not be submitted to an AI tool without your written consent covering the tool and the intended data. We only use providers and settings that do not train on your data. An engineer verifies every AI-assisted finding before it reaches you. Discuss provider retention and processing terms before consenting. Declining AI-tool use should leave a clear manual review path.
Deletion and handover
Agree storage location, permitted recipients and retention before access is granted. At handover, confirm which artifacts the customer keeps and when InfraNull’s copies of raw evidence and working files will be deleted. Ask for a written deletion confirmation; do not assume an unspecified retention period.
Trust through explicit scope
This page describes the boundaries we propose for an engagement. Your statement of work should record the details that apply to your environment.
We do not claim security certifications, regulatory compliance or a formal audit opinion. A readiness review can identify evidence gaps and technical risks; it cannot substitute for your compliance process.
Read the website privacy draft →A clear next step
Know what needs attention.
Then decide what to change.
A one-week, read-only EKS Production Readiness Review. $1,500. A prioritized plan your team can use.