From one process to standard practice.
How an AegisDatastra engagement runs: what happens in each phase, who does what, how it is deployed, and the support you get once it is live.
Start with one process. Prove it. Then extend.
Most organisations begin with a 6–12 week proof of value on one high-risk process, such as an agent workflow, a sensitive-data use or an audit requirement. Timelines and acceptance criteria are agreed before configuration starts.
- 01Scope
Choose the process, name a sponsor and an owner, and agree success criteria and data access.
- 02Connect
Read-only, metadata-first connections, each with an agreed role and scope.
- 03Configure
Map the process to controls, obligations and policies. Your people confirm every mapping.
- 04Prove
Run the process under governance and measure it against the criteria agreed at the start.
- 05Extend
Add the next processes, then overlay, extend or consolidate tools at your pace.
Clear responsibilities from the first week.
| Area | AegisDatastra team | Your team |
|---|---|---|
| Scope and success | Proposes success criteria and a plan for the proof of value | A sponsor and an operational owner; agrees the criteria |
| Access and security | Supplies the security documents and connection details your review needs | Security review, access approvals, test or synthetic data where needed |
| Connections | Sets up and tests each connector against its agreed role | System owners grant access and confirm scope |
| Controls and policies | Imports obligations, drafts control and policy mappings | Risk, compliance and control owners confirm every mapping |
| Approvals and exceptions | Configures approval routes and escalation | Names approvers and decides exceptions |
| Training | Role-based walkthroughs for administrators, control owners and approvers | Makes the right people available |
| Outcome review | Reports results against the agreed criteria, with the evidence behind them | Decides whether and where to extend |
Deployed where you need it. Supported by people.
SaaS, private cloud or your environment
SaaS is available today. In-region private cloud and customer-hosted deployment are agreed case by case. The hosting location is written into your contract.
Specialists who work with you
Forward-deployed specialists work on site or remotely in your time zone during setup, with a named contact for the engagement.
Service levels in writing
Support hours, response targets and service levels are written into your order form, so procurement reviews what you will actually receive.
Security, hosting and contract documents are listed on the trust page.
Implementation questions.
01How long does it take to get started?
Most organisations begin with a 6–12 week proof of value on one high-risk process. Timelines and acceptance criteria are agreed per engagement, before configuration starts.
02Do we have to replace our current GRC tools?
No. AegisDatastra sits beside your existing GRC suite, ITSM and security tools. Overlap is retired only at renewal, and only if you choose.
03What do we need to provide?
A sponsor, an operational owner, one process, access approvals for the systems involved, and control owners to confirm the mappings. Approved or synthetic test data is fine for the proof of value.
04What support do we get after go-live?
A named contact, role-based training for new users, and the support hours, response targets and service levels written into your order form.
Bring one process. Leave with proof.
Pick an agent workflow, a sensitive-data use or an audit requirement. In a 6–12 week proof of value we map it, govern it and hand you the receipts.
- 01Tell us the process
- 0230-minute walkthrough on your use case
- 03Scoped proof of value

