Security
Threat models, incident notes, detection rules and the reports nobody wants to write twice. 27 promptsSecurityVendor risk assessment against security and privacy standardsControl gaps, the evidence asked for, and the risk that stays after mitigations.SecurityTurn a breach write-up into a timeline and lessonsAttacker path, the control that failed, and what to change before the next one.SecurityTime-to-remediate as a progress graphThe series, the trend line and the quarter that needs explaining.SecurityThreat-model a personal plan before committingWhat could go wrong, how likely it is, and the hedge that is worth it.SecurityThe trends in a threat report, ranked by surpriseWhat changed since the last report, and what it implies for the next quarter.SecurityThe story behind the remediation numbersWhat improved, what stalled, and the decision that caused each.SecurityThe security questions to ask before building anythingThreats by asset, trust boundaries, and the question the design has not answered.SecuritySecurity news a busy engineer can act onWhat happened, how it affects you, and the patch or setting that closes it.SecuritySTRIDE per element for a system designEvery element, its threats, and the control that answers each.SecurityRead mail headers and say whether the sender is realAuthentication results, the real originating host, and the one line that gives it away.SecurityRead logs and separate the signal from the noiseThe anomaly worth paging someone for, the sequence around it, and the benign explanation first.SecurityRead a threat report through a panel of specialistsEach specialist's take, the disagreement between them, and the commands that follow.SecurityProof-of-concept URLs and validation steps from a reportThe endpoint, the request, and the response that proves it.SecurityProgram progress over time as a graph specAxes, series and the annotation that explains the dip.SecurityOpen ports and services read as a threat landscapeWhat the exposure enables, the weakest service, and the order to fix.SecurityOne vulnerability finding, written to be reproducedAffected asset, reproduction, impact and the fix, in that order.SecurityNarrative threat scenarios for a system or planThree plausible attack stories, each with the earliest observable signal.SecurityNASA-grade review of a prompt or a design for riskThe failure that costs a mission, and the constraint that prevents it.SecurityMine a threat report for what is new and actionableNovel techniques, the detection chance you have, and the action for this week.SecurityMake a finding reproducible and shortThe trimmed report, with the step that was missing added back.SecurityInvestigation notes into a GraphViz graphEntities, links, and the edge that carries the most risk.SecurityHow to check your own systems betterThe gap in the current pipeline, the check to add, and its cost.SecurityExplain what a sample does and how it spreadsCapabilities, persistence, network behaviour, and the indicators worth blocking.SecurityAttack techniques from an article into Sigma rulesDetection logic with the false positives named.SecurityA short security update for a newsletterThe story, the takeaway, and why a reader should care this week.SecurityA bug bounty report that gets triaged fastTitle, summary, steps, impact and the fix, in the order triagers read.SecurityA CTF solution written so someone can learn itThe vulnerability, the exploit, the dead ends and the fix.