RivasSec

Infrastructure. Security. Insight.

Field notes on infrastructure security, cloud hardening, Kubernetes, IAM, and OSINT by RivasSec.

Latest posts

IAM Blast Radius Is an Architecture Problem, Not a Policy Problem

Most IAM reviews start too late, after the account structure and trust boundaries are set. Least privilege isn't fewer actions; it's smaller failure domains.


Continue reading

The Discovery Layer Is Broken: Hiring as an Observability Problem

The senior engineering market has a routing failure, not a talent shortage: resumes and funnels index for keywords and discard the signal seniors depend on.


Continue reading

Adoption Is a Security Control: Notes from Paving a Road

A control developers route around isn't a control. Field notes on making the secure path the easy path: 40% less remediation time, 27% less pipeline latency.


Continue reading

IAM Roles That Fail Loud: Small Defaults, Big Difference

A small Pulumi library that treats IAM safety as a precondition: mandatory permissions boundary, no wildcard trust, no wildcard actions, every opt-out explicit.


Continue reading

The Trust Decay: Why Modern Hiring Has Become an Adversarial System

The tech hiring pipeline has shifted from talent discovery to risk mitigation. In 2026, the engineers who get hired are the ones who are hardest to doubt.


Continue reading

Hardening Kubernetes Deployments

Pod-level Kubernetes guardrails aligned with the Pod Security Standards Restricted profile: non-root, no caps, read-only FS, NetworkPolicies, SA hardening.


Continue reading

Taming the OOM Killer: Process Priorities on Linux

The Linux OOM Killer decides what dies under memory pressure. Protect sshd, mysqld, and other critical processes with oom_score_adj via a small script.


Continue reading

Catching a Nation-State Proxy: OSINT on Twitter

In 2012 I traced a state-aligned Twitter proxy tied to Venezuela's ruling party. OSINT lessons for spotting subtle, credential-phishing nation-state infra.


Continue reading

The 208.5-Day Kernel Bug: Uptime, Overflow, and Risk

A 2012 Linux kernel bug caused CPU lockups after 208.5 days of uptime due to an integer overflow in sched_clock(). RHEL 5/6 lesson: patch and observe uptime.


Continue reading