Skip to content

Security: i2ba/spec

Security

SECURITY.md

Security Policy

I2BA is a specification and reference-schema project. Security issues may therefore include both implementation-tooling vulnerabilities and specification flaws that could permit authority widening, confirmation bypass, unsafe retries, secret disclosure, plan substitution, or similar failures.

Sensitive reports

Please do not disclose exploitable security issues publicly before coordinated review.

Use GitHub private vulnerability reporting / Security Advisories for sensitive reports when available for this repository.

Non-sensitive specification issues

Ordinary specification ambiguities, interoperability questions, and non-sensitive security-model discussions may be filed as GitHub issues.

Important security invariant

I2BA implementations must preserve:

Interpretation does not grant execution authority.

A model, agent, parser, workflow, or other intent source must not gain capabilities beyond those explicitly admitted by the target host.

Out of scope

I2BA does not itself secure:

  • the operating system;
  • network transport;
  • model providers;
  • target applications;
  • execution backends;
  • cryptographic identity systems.

Those systems require their own security controls.

There aren't any published security advisories