Skip to the main content
CYBRARY
/ FORGE
Platform
Solutions
Labs and Scenarios
Demos
Resources
Search
Ctrl K
EN
Back to Anvil
Cybrary Forge
/
Forge Offensive
/
Anvil
/
Faq
Forge Offensive
Overview
Tester portal
Reviewer portal
Engagements
Calendar
Queue
Workload
Templates
Ask Anvil
Anvil AI home
Findings register
Scorecard
Render worker
Methodology
Red-team playbook
Attack-path map
C2 console
Web workbench
Blue-team mirror
Blue-team training
Defender playbook
Coverage gaps
Forge Anvil
Pentest kit
Engagement admin
Evidence repository
Forge Anvil · FAQ
Questions about local execution, scope and evidence
Plain answers for testers, engagement managers and security reviewers.
Back to Forge Anvil
Forge Anvil frequently asked questions
Program and execution
What is the Forge Anvil program?
Where do Anvil tools run?
What is the sealed edition?
Does Anvil replace the tester's operating system or tool expertise?
Scope and safety
How does Anvil enforce engagement scope?
Can a tester bypass those controls?
Does the AI approve testing or expand scope?
What happens when a command is outside scope?
What happens when the testing window closes during an engagement?
How are redirects, discovered hosts and DNS changes handled?
Can an emergency stop or device revocation halt work?
Evidence and review
What evidence does Anvil retain?
Can customers review evidence without the desktop app?
How does Anvil preserve the difference between evidence and a conclusion?
How are missing recordings or capture failures shown?
What does a retest add to the evidence chain?
Does evidence automatically go to the proprietary AI model?
Teams and closure
Can several testers work the same engagement together?
Who decides that a finding is final?
How does the desktop app know a tester may run a command?
What happens to credentials and leftovers found during testing?
What has to happen before an engagement can close?
Can a reviewer replay what happened?
Walk through the evidence
Review safety controls
CYBRARY