fsoc-portfolio - Sanitized case study of Operation fsoc: a defense-

项目说明

Operation fsoc: Case Study

A defense-first, multi-phase security engineering project I have been running out of my own homelab since August 2025. This repository is a sanitized writeup, not a runbook. Specific products, numbers, narrow category-le, architectural details, IP addresses, hostnames, domains, and script internals have been deliberately kept out.

It is run as a systems-engineering effort, not a series of one-off tweaks: a charter, a requirements specification with stable IDs, a requirements traceability matrix, architecture and interface control documents, decision records, as-built documentation, and a ion discipline.

What is here is the engineering process: the systems-engineering baseline, the threat model structure, the audit methodology, the design goals behind the monitoring scripts, and the integration lessons generalized to the class-of-trap level.

The documents (read in order)

| # | Document | What it covers |
|---|---|---|
| 1 | 1-O.pdf | What the project is, why I built it, high-le, defensive bias, organization, status |
| 2 | 2-ThreatModel.pdf | What I defend against, what I explicitly do not, the assume-breach table, se categories |
| 3 | 3-HardeningMethodology.pdf | The fi audit loop, the operational-health dimension, phase ordering, gating protocol |
| 4 | 4-ScriptsShowcase.pdf | Production monitoring automation at the goal level (no code, no layer mapping) |
| 5 | 5-LessonsLearned.pdf | Integration traps, generalized to the class-of-trap level |
| 6 | 6-Security.pdf | What is redacted, what is published, how to report a leak |
| 7 | 7-WorkstationMigration.pdf | Bringing the operator workstation under the same threat model; the residual risk it does and does not close |

LaTeX sources for all seven are in tex/.

*Revised 2026-06-15 (rev. 3): updated to today's state and the work planned next. Fleet authentication has finished its cutover to certificate-only access; an operational-health and capacity dimension was added to the monitoring after an outage the security audit could not ha; a reco milestone proved the backups actually restore, escrowed the backup encryption key off the fleet, and put a staleness alarm on the backups themselves; an unused service and a redundant external entry path were retired to shrink attack surface; execution of the change-management process is now go by a risk-classified automation layer with human appro; and the operator-workstation work has progressed to a self-healing layer, with a terminal-nati center being built on top. A planned physical relocation of the hardware is the next external deadline and doubles as a full-restore . The sanitization gate was extended again to cover the new tooling.*

Author

Gurmann Basran. Computer Science student, Founder at Phuturum Tech, aspiring security engineer. github.com/gbasran

*The li described in this case study is personal, and is not shared with Phuturum Tech's production infrastructure.*

License

MIT. See LICENSE.

项目信息

开发语言：TeX

Star 数：2

技术要点

该项目属于防护思路方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕Sanitized case study of Operation fsoc: a defense-first, multi-phase security engineering project. Threat model, hardening methodology, script design principles, and integration lessons, all redacted to protect live infrastructure.展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。