[GH-ISSUE #71] [Enhancement]: scope of work menu #42

New Issue

2026-06-06T22:08:12-04:00

yindo commented

2026-06-06 22:08:12 -04:00

Originally created by @s-b-repo on GitHub (Oct 25, 2025).
Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/71

Originally assigned to: @asdek on GitHub.

Target Component

Documentation and User Experience

Enhancement Description

this will help manage what can and cant be test based on contracts like ip blacklists from testing and websites etc or ip and subnets or services on certain ports

Technical Details

No response

Designs and Mockups

No response

Alternative Solutions

No response

Verification

I have checked that this enhancement hasn't been already proposed
This enhancement aligns with PentAGI's goal of autonomous penetration testing
I have considered the security implications of this enhancement
I have provided clear use cases and benefits

Originally created by @s-b-repo on GitHub (Oct 25, 2025). Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/71 Originally assigned to: @asdek on GitHub. ### Target Component Documentation and User Experience ### Enhancement Description this will help manage what can and cant be test based on contracts like ip blacklists from testing and websites etc or ip and subnets or services on certain ports ### Technical Details _No response_ ### Designs and Mockups _No response_ ### Alternative Solutions _No response_ ### Verification - [ ] I have checked that this enhancement hasn't been already proposed - [ ] This enhancement aligns with PentAGI's goal of autonomous penetration testing - [ ] I have considered the security implications of this enhancement - [ ] I have provided clear use cases and benefits

yindo added the enhancement label 2026-06-06 22:08:12 -04:00

yindo commented

2026-06-06 22:08:13 -04:00

@asdek commented on GitHub (Oct 25, 2025):

Hello @s-b-repo,

Great suggestion! This fits perfectly with our already planned scanning template functionality. We'll add this to our development roadmap.

We can also implement backend validation to prevent agents from going outside the defined scope during engagements.

If you have specific ideas on how the validation algorithm should work, especially considering the possibility of custom exploit development and mass scanning tool execution, please let us know 😉

@asdek commented on GitHub (Oct 25, 2025): Hello @s-b-repo, Great suggestion! This fits perfectly with our already planned scanning template functionality. We'll add this to our development roadmap. We can also implement backend validation to prevent agents from going outside the defined scope during engagements. If you have specific ideas on how the validation algorithm should work, especially considering the possibility of custom exploit development and mass scanning tool execution, please let us know 😉

yindo commented

2026-06-06 22:08:13 -04:00

@s-b-repo commented on GitHub (Oct 26, 2025):

Hello @s-b-repo,

Great suggestion! This fits perfectly with our already planned scanning template functionality. We'll add this to our development roadmap.

We can also implement backend validation to prevent agents from going outside the defined scope during engagements.

If you have specific ideas on how the validation algorithm should work, especially considering the possibility of custom exploit development and mass scanning tool execution, please let us know 😉

it should use .conf the agents are whitelisted to those if it goes out of scope or to third party testing instanlty kill it and restart adding a reminder

@s-b-repo commented on GitHub (Oct 26, 2025): > Hello [@s-b-repo](https://github.com/s-b-repo), > > Great suggestion! This fits perfectly with our already planned scanning template functionality. We'll add this to our development roadmap. > > We can also implement backend validation to prevent agents from going outside the defined scope during engagements. > > If you have specific ideas on how the validation algorithm should work, especially considering the possibility of custom exploit development and mass scanning tool execution, please let us know 😉 it should use .conf the agents are whitelisted to those if it goes out of scope or to third party testing instanlty kill it and restart adding a reminder

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#42