DGM Super IntelligenceINTELLIGENCE. WITH INTENT.Early access

DGM INTENT / EXPOSURE BASELINE / IN BETA TESTING

Turn your API security evidence into a decision.

For security engineering leads responsible for an internet-facing API estate, an Exposure Baseline is a proposed, bounded evaluation of whether DGM Intent helps your team investigate suspicious activity and identify visibility gaps.

DGM Super Intelligence · Updated

DGM Intent is in beta testing. Beta access is subject to availability and suitability. Joining the waitlist does not activate protection.

Start with one agreed estate, an observation window and a permitted source sample. Your team reviews the evidence and its limits, then decides whether to continue with a pilot, change the scope or stop. DGM Intent is in beta testing.

01

A clear investigation question

Choose a decision your team struggles to make today, such as whether repeated API probing fits authorised scanning or warrants further investigation. Name the analyst, security owner and source owners before agreeing the evaluation.

  • One bounded API or application estate
  • One agreed observation window
  • Success criteria set before reviewing findings
02

Use telemetry you are permitted to share

Review a representative sample of available API gateway, WAF or network records. The beta has representative Zeek and Suricata inputs; compatibility and useful fields must be assessed for your actual sources. Source access, minimisation, retention and transfer arrangements are agreed before sharing data.

  • No credentials or sensitive logs in an initial enquiry
  • Document source freshness, missing fields and gaps
  • Begin with passive investigation and no production changes
03

Know what you would receive

The proposed deliverables are a coverage inventory, an evidence pack with supporting and competing explanations, telemetry gaps and analyst-reviewed recommendations. Material interpretations should be traceable to permitted source records so your team can reproduce the reasoning.

  • Inspect the sequence behind a finding
  • Keep likely intent separate from observed facts
  • Record unknowns and the next useful source
04

Evaluate the beta honestly

Our demonstration uses synthetic scenarios. Software and lab checks do not establish customer detection effectiveness, complete coverage or a production service level. AI involvement and provider attribution remain unknown without explicit evidence. Protection and repair paths are being evaluated in controlled labs.

  • No guaranteed detection rate or universal protection
  • Consequential actions require explicit customer authority
  • Joining the waitlist does not activate protection
05

Agree the commercial scope before work

Availability and suitability are reviewed individually. Scope, dates, data handling, acceptance criteria and any fee would be agreed in writing. Pricing is discussed after sample and scope review; this page does not create a paid subscription or commitment.

  • Review a permitted sample and the buyer's question
  • Agree how the analyst and sponsor will assess value
  • Record a continue, change-scope or stop decision

RELATED DGM GUIDANCE

Continue exploring

Explore DGM Intent

The beta investigation workflow and its current limits.

Investigating AI-powered threats

Assess suspicious behaviour without assuming AI attribution.

Evidence and customer control

The principles behind a scoped evaluation.

DGM INTENT / IN BETA TESTING

Discuss your API estate.

Tell us your role, the investigation decision and the types of telemetry available. Please do not email credentials or private source records.

Discuss an Exposure Baseline