A machinist's dial indicator on a black granite surface plate in a dark calibration lab
Engineering

Built to be
audited.

Institutions do not adopt an attendance system on a promise. This is the process a change moves through before it reaches a classroom, the gate that can send it back, and the standards the process is written against.

How a decision becomes production

  1. D—01

    Frame

    The problem gets written down before anything gets built.

    Problem briefISO/IEC 12207
  2. D—02

    Decide

    Every option argued in writing. One-way doors get the scrutiny. The reasoning outlives us.

    Decision recordISO/IEC/IEEE 42010
  3. D—03

    Secure

    Threat-modelled before it is implemented. AEGIS publishes a root, never a name.

    Threat modelISO/IEC 27001 A.8ISO/IEC 29100
  4. D—04

    Verify

    Tests, security and accessibility. A failed gate goes back to the decision, not the queue.

    Verification gateOWASP ASVS 4.0WCAG 2.2 AA
  5. D—05

    Operate

    Shipped in stages against objectives. The review feeds the next decision.

    SLO + incident reviewISO/IEC 27001 A.5.24NIST CSF 2.0
Standards register

AYSA Labs builds aligned to these frameworks. They are the references our process is written against — not certifications held. Where a deployment requires audited certification, we say so in the contract.

ISO/IEC 27001:2022Information security management

Access control, logging and incident response for institutional data.

ISO/IEC 27701:2019Privacy information management

Data minimisation — no name or roll number leaves the institution.

ISO/IEC 25010:2023Software product quality

The quality model we hold releases against before they ship.

ISO/IEC 42001:2023AI management systems

Governance for the intelligent systems we build and deploy.

NIST CSF 2.0Cybersecurity framework

Identify, protect, detect, respond, recover — mapped to our runbooks.

DPDP Act, 2023Digital Personal Data Protection

The Indian statute our institutional deployments operate under.

Posture

What a reviewer
checks first

Three properties do most of the work in a security review. Each one is a design decision made early, not a control bolted on afterwards — which is why they hold.

01

No personal data leaves

AEGIS publishes a Merkle root and a record count to a permissioned chain. No name, no roll number, no identifier ever crosses the institution boundary.

02

Every change is attributable

Manual corrections require a reason and are written to a permanent change log. Finalised rosters lock. There is no silent edit path.

03

Students can check our work

A student verifies their own attendance record against the chain independently — the guarantee does not rest on trusting us.

Doing diligence on us?

Ask us the hard ones.

Threat model, data-flow map, change log format, what happens when the chain is unreachable — we will walk your security or IT team through any of it, in writing.

Start a security reviewEmail us directly