2AYE
Active Directory defense

Protect privileged directory changes with exact-action runtime authorization.

2AYE now registers certificate-pinned LDAPS connectors, confines changes to a configured base DN, prepares privacy-preserving exact-change fingerprints, consumes a single-use runtime authorization before LDAP execution, and records success or failure receipts.

  • Pinned LDAPS
  • Directory boundary
  • Exact change authority
What you can evaluate

Runtime-enforced Active Directory group and account control through guarded APIs.

01

Pinned LDAPS

Require port 636 and constant-time SHA-256 server-certificate pin validation.

02

Directory boundary

Refuse target or member distinguished names outside the configured base DN.

03

Exact change authority

Bind add member, remove member, or disable account to the agent, environment, connector, and hashed exact target.

04

Connector enforcement

Redeem once before LDAP and record an execution receipt; replay and parameter substitution never reach the adapter.

The enforcement path

Follow Active Directory defense from identity to evidence.

Each consequential action moves through the same six control points. See where 2AYE evaluates authority, requests human review, and preserves the outcome.

  1. 01IdentityWho or what is acting
  2. 02IntentSigned purpose and limits
  3. 03PolicyDeterministic evaluation
  4. 04ApprovalA named human when required
  5. 05ExecutionSingle-use grant, redeemed at the resource
  6. 06EvidenceReceipt joined to the audit chain
Deterministic decisionsSingle-use, exact-action grantsHash-linked evidence

Your next move

Put a boundary around privileged changes.

Choose a step.
See what matters for your workflow.

Focus / 01

Choose the directory object

Design exact approval for a privileged directory change.

Discuss this workflow
Active Directory defense

Interactive planning guide. Explore the steps without changing your setup.

Review the integration requirements and supporting evidence for this capability. Talk to us