in an effort to democratize secure by design we recently built a threat modeling copilot, part expert system-turned prompt engineer, part LLM; given an arbitrary system design we can now produce a fully elaborated threat model in context of our threat and control framework in minutes. we call this approach “tradecraft prompting”. innovations like this help engineers understand *why* controls are important not just *what* they need to do to build secure systems, while breaking the scaling problem of traditional threat modeling. feedback welcome, we hope this paper can be a valuable spark for furthering secure systems design. ... and stay tuned we've got some open source on the way designed to democratize detection. blog with link to technical paper and design here: https://lnkd.in/eKvMWny3. #securebydesign #securityengineering #ai
The testing methodology employed "tradecraft prompting," which encoded the on-the-ground knowledge of JPMorgan Chase threat modelers directly into the AI system's prompts. This approach was designed to capture decades of accumulated threat modeling knowledge and experience from the bank's cybersecurity teams. This comes as both pros and cons. The best PRO is the work can be highly applicable to banking. The CON is it's not translatable to non-banking domains, imo.
What I most appreciate about Cyber Security is the community it fosters. It is in all of our interests to collaborate and protect critical systems and customer data.
Kudos to your team Yassir Nawaz on this impressive offering. Access to cutting-edge, shift-left security offerings through well maintained f/osss can truly help SMBs, NPOs, and software teams that lack the resources to invest heavily in security. This will go a long way in bolstering the resilience of our entire digital ecosystem. Fantastic to see this direction — open source can drive stronger community-driven defenses and faster response to emerging threats. Looking forward to learning more about the “stay-tuned” part :)
Love this, Pat Opet. The "why" is so critical and is often overlooked.
Love the ground up innovating approach Pat Opet - the more we can do to easily show developers the “why”, the better we will be.
Get someone on your comms team to pop us a note when you drop the OSS to "democratise detection" Pat in case LI's algos don't surface it. Would be keen to have a look for The Stack. fyi Jennifer Lavoie
There are lots of efforts going in this direction. With the funding and talent at JPM and Matt at Citi there is likely going to a be a major jump forward in value and process efficiencies to the business from threat modeling. When these new capabilities in threat modeling start to build models and integrate into the risk programs to pull from, update to, and map controls to policies and risk/control registries then these tools become more than admin cost reduction and lead into major business process enablers. Stephen de Vries Jonathan Meadows Pat Opet Brian B. #threatmodeling
Outcome AI
1moStrong move Pat! Next step is audit-ready and outcome-driven. Provenance: lock model and prompt versions per run, log inputs and routing, keep results replayable Closure: establish a re-test cadence and show evidence high-risk paths remain secure KPIs: time to model, re-test pass rate, open-path count per application