Skip to content

Interview question · Security Foundations & Threat Modeling

Build a security programme for a 60-person startup using only open-source tools. What do you deploy, and what do you watch out for?

The tools are free; running them is not. A strong answer picks a small set by risk, assigns owners, and treats every security tool as software that can be compromised or relicensed.

mediumNewPreparation tags: Stripe, Shopify, CloudflareUpdated Nov 2026

The tools are free; running them is not. A strong answer picks a small set by risk, assigns owners, and treats every security tool as software that can be compromised or relicensed.

Make your first attempt

What would you say before reading the answer?

  1. 01 State the assumptions your answer depends on.
  2. 02 Explain the mechanism and choose a control.
  3. 03 Name a condition that would change your decision.

The worked answer includes an approach, scoring criteria and follow-up questions. Compare the reasoning with your own.

10 answers per topic instead of 5, plus saved progress and bookmarks · costs nothingor unlock all 529 remaining answers · $25

Every worked answer in all 17 topics, every lesson in every course, the full concept curriculum, the complete practice-test bank, and the downloadable security field guides.

6 months · One payment · No auto-renewal

What if · the follow-ups in this answer

The answer works through 4 follow-ups like an interviewer would

A 60-person SaaS startup with no security budget asks you to set up security tooling in a month. They use GitHub Actions, Kubernetes on a cloud provider, and laptops managed loosely. One engineer can spend half their time on it.

  1. What do you set up in week one?
  2. What goes into CI, and what blocks a merge?
  3. How do you protect the pipeline that runs these tools?
  4. What is the one-month plan?

Each rung has a nudge, a model answer, the principle that carries over and the weak answer to avoid. Premium opens every answer and ladder.

UP NEXT ON YOUR JOURNEY
DISCUSSION · 0

No comments yet. Share a correction or a different way to answer it.