AEGISGUARD

// AEGISGUARD LABS

Understand attacks
before attackers use them.

AegisGuard Labs researches AI-powered attack and defense techniques. By understanding the same technology attackers use, we prepare for methods that have not spread yet.

// RESEARCH TRACKS

Four research tracks

LAB-01STARTING

Social engineering with generative AI

Testing scams that use generated text, voice, and video, and building indicators to detect them.

RESEARCH QUESTIONS

  • ?How well can people and systems detect generated text, voice, and video?
  • ?Where in business processes is there room for impersonation to slip in?
LAB-02STARTING

Autonomous attack agents

Reproducing AI-agent reconnaissance and intrusion in an isolated environment to study where defenders can detect it.

RESEARCH QUESTIONS

  • ?At which stage does an autonomous agent leave traces for defenders?
  • ?How effective are existing detection rules against automated attacks?
LAB-03STARTING

Safety of LLM applications

Developing methods to evaluate prompt injection, data leakage, and permission overreach.

RESEARCH QUESTIONS

  • ?At which layer should instruction injection through external data be stopped?
  • ?What is a safe design standard for the permissions given to AI agents?
LAB-04STARTING

Automating defense

Decision criteria and operating design for safely automating everything from detection to isolation and remediation.

RESEARCH QUESTIONS

  • ?Under what conditions may isolation proceed without human approval?
  • ?How can the business impact of false positives be minimized?

// METHODOLOGY

How we research, and the rules we keep

ISOLATED

Isolated environments

Attack techniques are reproduced only in our own test environment, cut off from the outside.

NO LIVE TARGETS

No third-party targets

We do not probe or attack third-party systems without permission, even for research.

DUAL USE

Care about misuse

We do not publish concrete attack procedures or tools beyond what defense requires.

FEEDBACK

Return to services

What we learn is built into detection rules, assessment methods, and exercise scenarios.

// DISCLOSURE POLICY

Vulnerability disclosure policy

  1. 01

    Discover

    If we find a vulnerability in a third-party product during research, we assess its exploitability and impact.

  2. 02

    Report

    We report it privately to the vendor or maintainer, through a public coordination body where appropriate.

  3. 03

    Coordinate

    We allow time to prepare a fix and agree on the disclosure date with the vendor.

  4. 04

    Disclose

    After the fix, we publish information so users can protect themselves. We do not publish exploitable details.

To report a vulnerability in our own site or services, please use the contact listed in security.txt.

// PUBLICATIONS

Reports and technical articles

$ labs --publications --latest

> 0 items. The first report is in preparation.

> Please check back after launch_