APTOE: Governed AI-Native Penetration Testing Platform

The Problem and Why It Mattered

A Linux-first platform for authorized penetration testing that coordinates AI-assisted security work through exact approvals, sandboxed capabilities, encrypted evidence, and independent finding verification. The relevant technical and business risk is the cost of leaving this workflow, control, or product boundary unclear, manual, insecure, or difficult to operate. The case study focuses on the decisions used to make that risk manageable.

Objectives and Success Criteria

• Deliver the capability described in the project objective using a maintainable technical design.
• Make the main workflow, control boundary, and operational responsibilities explicit.
• Produce reviewable implementation evidence without publishing confidential values or customer data.

Requirements and Constraints

The product design had to balance a clear user workflow with maintainable technical boundaries, secure handling of user data, and a path for incremental delivery.

My Role and Ownership

I owned the technical design and implementation described in this portfolio record, including the technology choices, core system boundaries, and the documentation of the resulting approach. Related organisational decisions, vendor operations, and formal certification decisions remain outside the scope of this technical case study unless stated explicitly.

Solution Overview

The solution is built around Python, SQLite/WAL, PyQt6. Its implementation is organised as the components below so that the architecture, control points, and operating model can be evaluated separately rather than treated as a list of tools.

Architecture and System Design

The public architecture description follows the path from the initiating user, workload, or operator action through the relevant product development components. Access boundaries, data or state handling, and operational controls are described at a safe level; secrets, private addresses, and client-sensitive implementation details are intentionally omitted.

Technology Decisions and Trade-Offs

I selected Python, SQLite/WAL, PyQt6 because they support the project objective and make the critical engineering boundaries explicit. The trade-off is operational and platform complexity: the design depends on documented configuration, controlled access, and ongoing review rather than assuming that a managed service or framework removes engineering responsibility.

Implementation Walkthrough

The following implementation notes describe the components that matter most to the project outcome. They are intentionally focused on technical decisions and operating behaviour instead of reproducing entire source files or sensitive configuration.

Implementation: Durable daemon and bounded workers

The aptoed daemon owns sessions, task leases, append-only events, approvals, checkpoints, cancellation, recovery, and evidence metadata. PyQt6 and CLI clients use a local API; they do not directly own the engine database, provider credentials, or tool execution.

Implementation: Exact approval and scope control

Every consequential action is bound to a canonical capability, arguments, target, destination, signed scope, task lease, and expiry. Grants are one-use and fail closed when scope, action, or task state changes.

Implementation: Evidence and finding lifecycle

Tool or model output remains an observation until reproducible evidence, scope context, independent verification, and report QA support promotion. Sensitive artifacts use AES-256-GCM with OS-keyring-managed keys and redacted event streams.

Implementation: Release evidence and open gates

The documented Windows snapshot records 276 passing tests, seven Linux-only skips, one companion-service test, and 13 deterministic workflow-lab cases. Trusted Linux packaging, sandbox, authorized live-target, and production-service proof remain explicit release gates.

Challenges, Failures and Corrections

This portfolio record does not invent deployment failures, client incidents, or corrective actions that are not supported by the published project evidence. Where operational details are confidential or were not captured for public release, the case study documents the design boundary and lesson instead of presenting an unsupported narrative.

Security, Compliance and Risk

The public record avoids secrets, customer data, and private infrastructure details. The relevant security controls, access boundaries, and operational risks are addressed in the implementation notes where they are material to the project.

Testing, Validation and Evidence

The evidence published for this project is the documented implementation, its stated architecture and controls, and the portfolio record. Replaced a client-owned workflow with a daemon-owned execution model that preserves durable sessions, exact approvals, encrypted evidence, and recovery state. The documented Windows validation snapshot records 276 passing tests, seven Linux-only skips, one companion-service test, and a 13-case deterministic workflow-lab pass. Claims are limited to the implementation details and outcomes documented in this case study.

Results and Evidence

Replaced a client-owned workflow with a daemon-owned execution model that preserves durable sessions, exact approvals, encrypted evidence, and recovery state. The documented Windows validation snapshot records 276 passing tests, seven Linux-only skips, one companion-service test, and a 13-case deterministic workflow-lab pass.

What I Learned

This project reinforced that product development work is not a technology checklist. The durable value comes from making boundaries, trade-offs, ownership, and evidence clear enough for another engineer or stakeholder to review and operate the system responsibly.

What I Would Improve Next

• Expand automated validation around the most important workflow and control boundaries.
• Add or deepen operational evidence, such as dashboards, test artefacts, or an architecture diagram where it is safe to publish one.
• Review the design against the next expected scale, reliability, and governance requirement before extending the system.

Final Takeaway

This security engineering, systems architecture, and developer tooling case study addresses a defined technical problem through Python, SQLite/WAL, PyQt6. It demonstrates my ability to turn requirements into an explainable design, implement the important controls, and document outcomes and limitations without overstating what the evidence proves.