Pentforge.app

AI security.
Clear boundaries.
Accountable action.

Understand what your models can access, what your agents can change, and what evidence your team needs to act.

Start with the business workflow. Explore the controls, agree who owns the risk and define the work before it begins.

Define your engagementOpen your workspace

Interactive scoping aid. No live testing or changes are performed here.

Keep retrieved content inside its permission boundary.

A documented boundary between your data, the model and its users.

  • Review which documents each identity may retrieve.
  • Treat retrieved instructions as untrusted input.
  • Define what the assistant can return or send to a tool.

One estate. Connected controls.

Choose a control to trace its review focus and supporting references.

AetherOPSReview coordinationModel robustnessRelease evaluationsAgent permissionsData boundariesAuthorised scopeEvidence & remediationModelScanGuardrailsAetherOPSModel robustnessRelease evaluationsAgent permissionsData boundariesAuthorised scopeEvidence & remediation
Supporting references

ModelScan · Guardrails

Review map for document assistant. Connections express review relationships, not live telemetry or tool execution.

Model & input controls

Retrieved documents and model inputs cross trust boundaries.

Review focus
Inspect retrieval permissions, untrusted instructions, model files and output-handling rules.
Proposed deliverable
Trust-boundary map and control recommendations
Decision to agree
What data may the assistant retrieve, return or send?

Adapter references · availability confirmed per deployment. References in this map do not establish installation or customer readiness.

Scope this work

Turn observations into
decisions and verified change.

Assessment, remediation and maintenance are separate commitments. Each needs clear ownership, agreed effort and evidence.

  1. Assess the exposure

    Confirm systems, authorisation, methods and review criteria. Practitioner review separates an observation from a validated finding.

  2. Scope the remediation

    Agree approved changes, owners, rollback planning and verification. Implementation support is a separately scoped project.

  3. Maintain the evidence

    Define an optional maintenance retainer for recurring reviews, evidence upkeep and agreed retests. Capacity and response windows are written into the proposal.

Built with the open-source ecosystem.

AetherOPS and Pentforge build on multiple open-source projects, alongside our own application and integration work. The application foundation and referenced security adapters have different readiness levels.

Upstream names, licences and attribution remain with their respective projects. A reference is not a claim that a tool is installed, enabled or approved for a customer environment. Inclusion does not imply endorsement or partnership.