SECURITYCORPPublication active
Field notes
Field note // 001Independent security field notesEst. 2026

Security is a
practice.

Hands-on guides, honest lab notes, and defensive systems built to fail safely. Written for engineers, learners, and the relentlessly curious.

Explore the field notes

CURRENT SCOPE / 04

  • 01Container & Kubernetes security
  • 02Detection engineering
  • 03Secure self-hosting
  • 04Cloud & identity
Last documented state: Aug 28, 2026

The premise

Good security writing should show the tradeoffs, failures, and evidence—not just the final configuration.

SecurityCorp documents real builds from the first threat model through the last regression test. Private details are removed; useful lessons stay intact.

Publication activity

Build log.

A running record of what's been written, verified, and planned — not a live system feed.

  1. Aug 28, 2026Published

    Fail-closed malware gate architecture

    Staged intake, explicit state machine, and release verification, written up as a full guide.

  2. Aug 24, 2026Validated

    VPN-bound container egress, verified

    Namespace sharing, egress proof, and kill-switch testing documented and confirmed against a live stack.

  3. Aug 18, 2026Documented

    Private reverse-proxy rollback pattern

    Split DNS, constrained management plane, and commit-confirm rollback, written up as a guide.

  4. 2026Planned

    Kubernetes parity migration

    A zero-change migration plan for existing services — still in design, no production cutover yet.

Latest intelligence

Guides from the lab

View all guides
01
Detection Engineering12 min readIntermediate

Building a fail-closed malware gate for automated downloads

How to keep untrusted files away from media services until scanning, verification, and release all succeed.

02
Container Security10 min readIntermediate

Proving a container can only reach the internet through a VPN

A practical verification method for network namespaces, kill switches, DNS behavior, and restart persistence.

03
Home Lab Security9 min readFoundational

A safer reverse proxy pattern for a private home lab

Split DNS, isolated listeners, internal TLS, and rollback planning without publishing services to the internet.

Control under test

What happens when it breaks.

Pick a failure condition. Every result below is either directly validated or documented as the intended design — none of it is a live simulation.

Failure injection
The malware scanner is unreachable or times out mid-scan.
Expected safe state
The file stays in isolated staging. It is never released on a timeout.
Observed result
Validated: a scanner outage was simulated deliberately and the release step never ran. Validated
Principle
Fail closed — an unclear result is treated as unsafe, not as a pass.
Read the full test

Selected builds

Systems, not demos.

Real infrastructure, instrumented and tested. Each project records its assumptions, controls, and known limitations.

P-01 Validated

Fail-Closed File Intake

A staged malware-scanning pipeline that prevents downstream import until completion, scan, and move verification all pass.

ClamAVPythonDocker
View case study
P-02 Operational

VPN-Isolated Workloads

A shared-network-namespace design with controlled LAN access, verified tunnel egress, and kill-switch regression checks.

GluetunNetworkingContainers
Read the guide
P-03 Operational

Private Service Gateway

An internal reverse proxy with split DNS, isolated management access, internal TLS, backup, and tested rollback.

NginxPKIDNS
Read the guide
P-04 Design

Kubernetes Parity Migration

A zero-change migration plan that preserves ports, paths, credentials, networking behavior, data, and recovery semantics.

K3sArchitectureGitOps
Open the project index

Your operator

Ravi Teja Thota

Writes SecurityCorp from the point where architecture diagrams meet inconvenient reality — Kubernetes, cloud, and detection engineering, tested before they're published.

CKACKSCKADCRTPAWS SAA
More about the author