Security Doesn't Have To Be a Nightmare
summary
Argument: move from late-stage security checks to shift security left by asking how the project’s CIA triad (confidentiality integrity availability) can be broken. Practical fixes: sanitize input, validate all data, and keep no credentials in repo. Tooling evidence: add automated scanners — DAST and SAST — into CI and PRs to catch injection and leakage early. Outcome claim: fewer last-minute fixes, cheaper design changes, and measurable reduction in risky commits.
AI-written summary · about
chapters (6)
- 0:00Start
- 7:37SANITIZE THE INPUT
- 8:53VALIDATE THE DATA
- 10:52NO CREDENTIALS IN YOUR REPO
- 25:47HOW CAN THE CIA OF THIS PROJECT BE BROKEN?
- 28:09SHIFT SECURITY LEFT
related talks
23mSecurity Doesn't Have To Be a Nightmare
37mSecurity Doesn’t Have To Be a Nightmare
24mGreat Security Is One Question Away
01h 04mShifting Security Everywhere
34mEmbarking on Your Security Journey
31mSharing Security Secrets: How to Encourage Security Advocates
40mMaking Security an integrated part of the SW Dev Lifecycle
38mPrioritizing Trust While Creating Applications