Recurring Attack Surface Mapping, Human Validated Testing, and Retest Cycles

Your Environment Changes Every Sprint. So Should the Test

An annual penetration test describes your environment on the day it ran, and the next release, cloud resource or permission change makes that report stale. GDF continuous AI penetration testing proves, cycle after cycle, which of those changes opened a real path to your data. AI tooling remaps the attack surface on an agreed cadence, and senior testers validate every new path by hand and retest every fix.

Isolated test laptop connected to a network appliance.

Testing on your release cadence

Exposure Tracked Between Every Release

New endpoints, new cloud resources, new integrations and changed permissions open exposure between scheduled tests, and an attacker does not wait for next year's engagement. Our recurring program applies AI assisted discovery and human validation to the systems in your scope on an agreed cadence, so the attack path created by last Tuesday's deployment is examined before someone else finds it. Each cycle starts from the previous cycle's evidence, which means your team sees what changed and what that change made reachable.

Want to see the method inside a single engagement first? Read how AI powered penetration testing works, or scope a one time network and application penetration test.

Scope Your Assessment

A Living Asset Map

Networks, applications, APIs, identities and cloud access rediscovered each cycle, with the changes since the last one flagged.

New Paths Proven or Ruled Out

Every candidate path the tooling proposes is run by a tester, who records whether it succeeded or a control stopped it.

Fixes Retested Next Cycle

Agreed corrections are verified against the original evidence and carried forward until each one is closed.

A Yearly Report Cannot Keep Up With a Pipeline

Teams that ship weekly change their attack surface weekly. A new API route lands without the authorization check its siblings have, a developer grants a storage role broader rights to fix a deadline, an integration adds a service account nobody reviews. None of that appears in a report written three months ago, and all of it is visible to an attacker the day it goes live.

GDF uses AI to remap that exposure, hunt for candidate weaknesses and correlate them into a proposed attack plan. Experienced testers decide what runs, separate real findings from false positives and hand your engineers remediation priorities they can act on in the next sprint.

If your release cadence has outrun your testing schedule, a senior tester will propose a cadence that matches it.

Scope Your Assessment

From discovery to demonstrated impact

Six Stages That Repeat as Your Environment Changes

Each cycle turns a large volume of discovery data into a short list of tested paths, and a tester stands between every possible path and a confirmed finding.

  1. 01

    Map the attack surface

    We identify the systems and connections in scope.

    We discover and organize the authorized networks, applications, APIs, identities and cloud access so the plan reflects the assets and connections that exist today, not the ones on last year’s diagram.

    The connected asset map records the discovery context for later analysis.

  2. 02

    Find candidate weaknesses

    We evaluate the discovery results for weaknesses worth a controlled test.

    We compare discovery results, configurations and security signals to find the gaps that merit a controlled test rather than another alert.

    Candidate findings stay linked to their supporting observations for tester review.

  3. 03

    Connect the possible attack paths

    We rank hypotheses into a proposed attack plan.

    We connect weaknesses, permissions and trust relationships into possible paths to sensitive information or critical systems and name the prerequisites that would have to be true.

    The plan ranks hypotheses for testing instead of treating a possible path as an established compromise.

  4. 04

    Review the proposed test plan

    A tester approves what is permitted to run.

    A GDF tester checks the evidence, prerequisites, scope and operational risk before approving the plan, so proposed activity stays inside the authorized boundaries.

    The reviewed plan identifies the tests approved by the human team.

  5. 05

    Validate the security impact

    We run the permitted paths and record what happened.

    Human testers execute the approved plan, reproduce findings and document the paths that succeeded and the paths a control blocked, so the record shows what was actually demonstrated.

    The resulting evidence records the demonstrated impact and the conditions behind it.

  6. 06

    Retest fixes and update the evidence

    We check agreed corrections and refresh the map.

    We retest the agreed fixes and carry new discoveries and environment changes into the next cycle, so each assessment starts from updated evidence.

    The retest record separates verified corrections from open risks and items needing further examination.

Repeat as the environment changes. New assets, releases, permissions and threat information feed the next agreed testing cycle.

One Application, One Identity, One Storage Bucket

A typical path

Internet facing applicationOverprivileged service identitySensitive cloud storage

The tooling correlates three observations from the latest cycle and raises a question: could a flaw in this application reach customer data through the identity it runs under? A tester confirms the prerequisites are real and the test is authorized, then runs it.

The report separates a demonstrated path from one that was plausible but not proven. When a control blocks the access, that result goes on the record as well, so the board hears what an attacker could actually do rather than what a diagram suggests.

If one application or identity worries you most, call (800) 868-8189 and we will build the first cycle around it.

Choose the Cadence That Matches Your Change Rate

Release driven cycles

Testing windows tied to major releases or deployment milestones, for teams whose risk changes with each launch.

Scheduled monthly or quarterly cycles

A fixed rhythm for estates that change steadily, with discovery intervals set by the technologies in scope and the value of the data they hold.

Targeted cycles for a high value system

A narrower program focused on one customer facing application, one cloud tenant or one identity platform that carries most of the risk.

Every option comes with agreed human testing windows, escalation contacts, retest coverage and stop conditions. Staffing and response commitments are written into the engagement so everyone knows who is working, when and on what.

Program Design Led by Credentialed Examiners

Every program is designed and reviewed by people whose names are on the report, and the testers assigned to yours are named before the first window opens. Founder, CEO and CTO Joseph Caruso holds the CISSP; read the team biographies.

What Your Security Team Receives Each Cycle

An attack surface record listing the assets and relationships examined and what changed since the last cycle. Prioritized findings that connect each validated weakness to the affected systems, the business impact and the evidence. Remediation guidance that names the action that breaks the path, and retest results showing which corrections worked and what is still open.

Priorities reflect reachability, the data affected and your operating context rather than a scanner score, so the first item on the list is the one that would hurt most.

Call (800) 868-8189 or request a free consultation to plan this work around your operation.

Rules of Engagement Written Before the First Cycle

We agree the systems, accounts and data that may be examined, the permitted techniques, the testing windows and the escalation contacts. Anything that could affect availability or sensitive data gets explicit treatment in the plan, with stop conditions your operations team has seen in advance.

The engagement also fixes the approved AI tools, where information is processed and which records are retained. Credentials, source code and sensitive findings travel only through approved workflows, and your team always knows what is being tested, by whom and how the evidence is handled. Test planning and reporting can be mapped to NIST SP 800-115, the Technical Guide to Information Security Testing and Assessment, when your auditors ask for a reference method.

The first conversation is free and starts the scope with you. Request it now.

Free planning guide

Settle Scope and Windows Before the First Cycle

The Penetration Test Readiness Checklist covers the decisions a recurring program depends on: which systems are in scope, who owns them, when testing may run, who signs the authorization and when fixes will be retested. The workbook pack adds a CSV scoping matrix and an obligation register your team can keep current between cycles.

Download the Readiness Checklist (PDF) Rate this resource or leave a suggestion Download the Scoping Matrix (ZIP with CSV)

Read the readiness checklist online and share it with your audit team.

Questions About Continuous AI Penetration Testing

Is this an automated vulnerability scan?

No. A scan produces observations. This program adds correlation, human review, authorized exploitation and evidence of impact, and every scanner result or AI proposed path stays a candidate until a tester validates it.

Will AI execute attacks without a tester reviewing them?

No. Human review comes before execution. GDF testers approve the proposed plan and run the authorized tests within the agreed scope, and a model cannot widen that scope.

Does continuous mean someone is testing our environment around the clock?

Continuous means a recurring program. Discovery intervals, human testing windows and any response commitments are set in the engagement to match how fast your environment changes.

Can AI find vulnerabilities that people miss?

AI can hold far more combinations of assets, permissions and observations in view than a person can, which surfaces candidate paths worth testing. A tester then proves whether each one is a real weakness in your environment.

Does this test our own AI models and chatbots?

This program uses AI to test your environment. Assessing your AI applications, models and their integrations is our AI security testing engagement, and the two can run side by side.

How is a program priced?

Price follows scope and cadence. The first call is free and covers the systems to include, the cycle frequency that fits your release rate, the timeline and the pricing.

Set the Scope and Cadence With a Senior Tester

Tell us which networks, applications, APIs and cloud environments must stay under review, how often they change and what you most need to protect. A senior tester will use the first call to recommend the scope, the cycle frequency and the evidence each cycle should produce, and that consultation is free.

Scope Your Assessment Call (800) 868-8189

Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .

Talk with an examiner

Discuss AI Testing

Tell us the systems, evidence and deadline. We can review relevant experience, potential conflicts and the scope before engagement.

Since 1992 · 24/7 dispatch · Court tested experts

Or call (800) 868-8189

Email or phone is required. For an active incident, please call. Read what we send with the request.

Privacy center

Choose your site settings

Optional technology stays off until you choose otherwise. You can change these browser settings at any time. Access to the core site does not depend on optional technologies.

Technology preferences
Sale or cross-context sharing: not used GDF does not sell or share website personal information for cross-context behavioral advertising.