Security & Trust

Security and trust begin with bounded authority and evidence.

Use only the scope required for the evaluation, preserve institutional authority, and make evidence reviewable.

Explore Controlled Evaluation

Public trust posture

Bound the workflow. Minimise data. Preserve authority.

These principles guide each evaluation profile and its technical review.

01

Bounded evaluation

Controlled Evaluation begins with one defined workflow and explicitly approved evidence.

02

Data minimisation

Map only the inputs or model outputs needed for the agreed evaluation question.

03

Execution profile

Evaluation location, data movement and access controls are defined for the agreed profile; customer-local execution can be considered where appropriate.

04

Authority remains separate

Customer-action and production-change authority remain with the institution throughout the evaluation.

05

Evidence discipline

Versioned evidence, declared scope and reproducible verification support reviewability.

Evaluation security profile

Define the controls required for the agreed scope.

The institution and AEGI establish the relevant data, access and review conditions before confidential evidence is exchanged.

01

Scope only the workflow, evidence and participants required for the evaluation question.

02

Define execution location, data movement and access controls for the selected profile.

03

Keep customer-action, production-change and stop authority with the institution.

04

Use a mutually approved privacy, security and contractual path for confidential evidence or customer data.

Public technical evidence supports initial diligence. Institution-specific security review and production approval remain part of the customer’s own decision process.

START WITH PUBLIC-SAFE CONTEXT

Discuss one bounded workflow.

Do not send customer records, credentials or security-sensitive material through the public website.

Start a Discussion