vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-20 12:37:04 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[GH-ISSUE #235] RFC: Cryptographic evidence chain for PentAGI pentest operations #83

New Issue
Open
opened 2026-06-06 22:09:01 -04:00 by yindo · 0 comments
yindo commented 2026-06-06 22:09:01 -04:00
Owner
Copy Link
Copy Source

Originally created by @tomjwxf on GitHub (Apr 5, 2026).
Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/235

Problem

PentAGI runs automated penetration testing with AI agents. Security assessments produce findings that need to be demonstrably authentic and tamper-proof — a modified pentest report could hide vulnerabilities or fabricate findings. Currently, there is no cryptographic evidence chain proving what tools were run, what was discovered, and that the results are unmodified.

Proposal

Integrate Ed25519 receipt signing into PentAGI's tool execution pipeline. Each pentest tool invocation would produce a signed receipt creating a verifiable evidence chain:

Recon (receipt_001) → Port Scan (receipt_002) → Exploit Attempt (receipt_003) → Report (receipt_004)

This transforms pentest results from "trust me" reports into cryptographically verifiable evidence packages.

Reference

protect-mcp (MIT, v0.5.3). Receipt format: IETF Internet-Draft. The receipt chain/DAG visualization is built-in via npx protect-mcp trace <id>.

Happy to discuss and contribute.

Originally created by @tomjwxf on GitHub (Apr 5, 2026). Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/235 ## Problem PentAGI runs automated penetration testing with AI agents. Security assessments produce findings that need to be demonstrably authentic and tamper-proof — a modified pentest report could hide vulnerabilities or fabricate findings. Currently, there is no cryptographic evidence chain proving what tools were run, what was discovered, and that the results are unmodified. ## Proposal Integrate Ed25519 receipt signing into PentAGI's tool execution pipeline. Each pentest tool invocation would produce a signed receipt creating a verifiable evidence chain: ``` Recon (receipt_001) → Port Scan (receipt_002) → Exploit Attempt (receipt_003) → Report (receipt_004) ``` This transforms pentest results from "trust me" reports into cryptographically verifiable evidence packages. ## Reference [protect-mcp](https://github.com/scopeblind/scopeblind-gateway) (MIT, v0.5.3). Receipt format: [IETF Internet-Draft](https://datatracker.ietf.org/doc/draft-farley-acta-signed-receipts/). The receipt chain/DAG visualization is built-in via `npx protect-mcp trace <id>`. Happy to discuss and contribute.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#83
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?