Stacks

50-person SaaS startup

A 50-person SaaS startup with a small, generalist IT/security team (no dedicated SOC), a remote-friendly engineering culture, dozens of third-party SaaS tools in daily use, and a budget that favors managed and freemium options over heavyweight enterprise suites.

A lean, cost-conscious starter stack covering the identity and endpoint fundamentals most startups need first: centralized SSO, phishing-resistant MFA, just-in-time infrastructure access for engineers, managed endpoint detection, and basic device management.

Solo founder

A one- or two-person, pre-seed to seed-stage startup founder who is also the company's entire IT and security function, running everything from a laptop and a handful of cloud accounts, with no budget for dedicated security headcount or enterprise contracts.

The absolute minimum viable security stack: free and freemium tools that piggyback on infrastructure the founder already has (Microsoft 365, a cloud account, a GitHub repo) rather than adding new subscriptions, covering the handful of risks most likely to actually bite a solo operator.

Mid-market SOC

A 500-2,000-employee company with a small, dedicated security team of perhaps three to eight people running a real, if lean, security operations function — a mix of in-house analysts and outsourced help, moderate compliance pressure from customers and regulators, and a budget that has to stretch across the whole security program rather than concentrate on one area.

The classic mid-size security team's stack: centralized identity and MFA, EDR and device management, a cost-effective NGFW and SASE pairing, native email and CNAPP protection, developer-integrated AppSec, a cloud SIEM paired with lightweight SOAR and vulnerability management, and the compliance automation and awareness training a growing company needs to keep closing enterprise deals.

Enterprise defense-in-depth

A multi-thousand-employee enterprise operating across regions, with dedicated security engineering teams, regulatory obligations, and enough staff to run overlapping controls from several vendors.

This stack deliberately overlaps controls: an email gateway plus behavioral detection, a CNAPP plus container runtime security, and separate endpoint, IGA, and PAM products. The tradeoff is more operational work in exchange for fewer single points of failure.

Cloud-native DevSecOps

An engineering-led technology company running its product entirely on containers, Kubernetes, and public cloud infrastructure, where a small platform or security engineering team embeds controls directly into CI/CD pipelines rather than running a traditional SOC, and developers are expected to fix what their own pipeline flags.

Security built into the delivery pipeline rather than bolted on afterward: cloud posture and infrastructure-as-code scanning, container image and runtime protection, SAST/SCA/DAST wired into pull requests, short-lived infrastructure credentials instead of standing secrets, and lightweight automation — leaving the traditional endpoint and email layers thin because this org's real attack surface is the cloud and the pipeline.

Student home lab

A student or career-changer studying for a certification like Security+ or OSCP, or just teaching themselves cybersecurity hands-on, running everything on a spare laptop, an old PC, a handful of VMs, or a Raspberry Pi — with essentially no budget and a strong preference for open-source tools whose source they can actually read.

A zero-cost toolkit spanning nearly every domain in this landscape, chosen for learning value over production polish: a self-hosted firewall and IAM server to configure by hand, network monitoring and packet analysis tools to watch traffic, the standard offensive-security OS and exploitation framework, open-source SIEM/EDR and forensics tools, and a home-lab-scale taste of threat intel, incident response, and GRC — everything a learner needs to practice the full attack-and-defend lifecycle without spending a cent.