Pilots by invitation · The Digital Foundry is the build studio of Digital Edge · Pricing on request

Home / Security & governance

security & governance

Governed from the first commit.

Security reviews kill more agent projects late than any model limitation. We design the controls in from the start, so the review confirms what is already there.

design standards

The controls we build to.

These are the standards every build is designed against. The specific controls for your build, and who operates each one, are documented and agreed in the scope.

access/

Least-privilege access

Each agent gets its own identity and only the permissions its task needs. No shared credentials, no standing access to systems it does not use.

data/

Data minimisation

Agents see the personal information the task requires and nothing more. We agree in scope which data may be used, where it is processed and how long it is kept.

oversight/

Human oversight

Decisions with legal or material effect on a person stay with a person. Agents prepare, check and recommend; people decide. This is how we design for POPIA section 71.

logging/

Logging and audit trail

Every action an agent takes is logged with its inputs, output, the rule or source it relied on, and who approved it, so any decision can be explained after the fact.

grounding/

Grounded outputs

Answers and drafts are generated from your approved sources, with the source cited. Low-confidence results are held for review rather than passed on.

testing/

Testing before release

We test on real cases, including the awkward ones, against the success criteria agreed in scope. Known limits are written down and shared, not discovered later.

monitoring/

Monitoring and failure handling

Production builds report volumes, exceptions and errors to the workflow owner. When an agent cannot complete a task safely, it stops and hands the case to a person.

residency/

Hosting and cross-border transfer

Where data is processed is agreed per build. If personal information leaves South Africa, we design for the safeguards POPIA section 72 requires.

change/

Change control

Changes to prompts, models, rules or integrations are versioned, tested and approved before release, with a route back to the previous version.

vendor/

Vendor neutrality

We do not resell a platform. Models and tools are chosen for the task and your environment, and designed so they can be replaced.

popia section 71

Automated decisions need a human route.

Section 71 of the Protection of Personal Information Act limits decisions that have legal consequences for a person, or affect them to a substantial degree, where the decision is based solely on automated processing that profiles them.

Where an automated decision of that kind is permitted, the person must be able to make representations about it, and must be given enough information about the underlying logic to do so.

We design for this by default: agents prepare and recommend, a person decides where section 71 applies, and the log records the logic behind every recommendation. Read the design note.

ai governance advisory

Policy and oversight at board level.

The Digital Foundry builds to your governance framework. If you need one written, or need AI governance reviewed across the organisation, Digital Edge, our parent, advises on AI governance for South African financial services.

Digital Edge

next step

Need the security conversation first?

Tell us about your environment and constraints. We will show you how a build would be governed before we discuss what it would do.