- How is customer data protected?
- We work in the customer's own tenant and environments wherever possible, under least-privilege access granted for the engagement and removed at its end. Where documents must be exchanged, they move through customer-approved channels and are classified before they are shared.
- Where is data stored?
- In the customer's environment and region unless the engagement explicitly agrees otherwise. Residency requirements are captured during Discovery and reflected in the architecture rather than resolved late.
- Do you support regulated industries?
- Yes. Our concentration is government, healthcare, financial services, and other regulated enterprises where control evidence and audit readiness are part of the delivery, not a separate exercise.
- How do engagements begin?
- With a scoped conversation, then a short assessment that produces a written baseline: obligations in scope, current posture, prioritized findings, and a sequenced plan with owners.
- What Microsoft technologies do you specialize in?
- Azure platform and landing zone design, Microsoft Entra identity, Microsoft 365, Microsoft Purview data governance, Microsoft Defender and Sentinel for security operations, Microsoft Fabric for data, and Azure AI services. These technologies are referenced descriptively; EAX Systems claims no Microsoft partnership, certification, or authorization.
- Is EAX Systems certified to ISO 27001 or SOC 2?
- No. Both are on our roadmap and are labelled as such on this page. We will publish the scope and date only when an examination or certification has actually been completed.
- Can you sign our security addendum or DPA?
- We review customer security addenda, data processing agreements, and confidentiality terms as part of contracting, and we tell you plainly which obligations we can meet before signature.
- Who has access to our environment during an engagement?
- A named team, listed in the engagement documentation, with individually granted access scoped to the work. Shared credentials are not used, and access is reviewed at each stage boundary.
- How do you handle privileged access?
- Through customer-approved just-in-time elevation with approval and logging, rather than standing administrative rights held for the duration of a program.
- How is AI used in your delivery work?
- As assistance for drafting, mapping, and summarizing, with a named reviewer accountable for the result. AI does not approve a control, accept a risk, or make a compliance determination.
- Will our data be used to train models?
- No. Customer data is not used to train models. Where an AI service is part of a solution, the data boundary and retention behaviour are documented before the service is connected.
- How do you report security issues found in our estate?
- Findings are recorded with severity, evidence, and a recommended remediation path, raised to the accountable owner directly when severity warrants it rather than waiting for the next report cycle.
- How should someone report a vulnerability to EAX Systems?
- Email info@eaxsystems.com with the detail required to reproduce the issue. We acknowledge receipt, investigate, and respond with our assessment and any remediation plan.
- What happens to our documents after an engagement ends?
- Deliverables are handed over to the customer. Working material held by EAX Systems is retained only as long as the contract and our records obligations require, then disposed of.
- Do you subcontract delivery work?
- When specialist capability is required, any subcontracting is disclosed and approved in advance, and the same access, confidentiality, and control expectations apply.