[OneDev #10] feat(security): establish red/blue team security cycle for PCT infra #31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Imported from OneDev issue #10 (id 35250)
Original project: internal-joseph
Original state: Open
Original submitterId: 5
Original submitDate: 2026-04-09T17:04:08.830+00:00
Original lastActivity: {'date': '2026-04-09T17:04:08.830+00:00', 'description': 'opened', 'userId': 5}
Original fields:
Idea
Implement a recurring red-vs-blue security cycle for PCT's own infrastructure. Red phase: simulate attacks against exposed surfaces (Caddy reverse proxy, Dex SSO, OneDev, sshubble, LXC/VM guest escapes, WireGuard endpoints, pctbin.com). Blue phase: harden, patch, and improve detection based on findings. Rotate between phases on a defined cadence (monthly or quarterly).
Why
PCT's infra has grown significantly — 30+ VMs/LXCs, multiple public endpoints, SSO, secrets API, RDP/SSH access. No structured security review exists. A red/blue cycle builds institutional knowledge of the attack surface, catches drift between deployments, and keeps both offensive and defensive skills sharp. Findings feed directly into hardening tasks and runbook updates.
Open questions