<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Identify on tplat</title>
		<link>/docs/threat-modelling/identify/</link>
		<description>Recent content in Identify on tplat</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<atom:link href="/docs/threat-modelling/identify/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Elevation of Privlege</title>
				<link>/docs/threat-modelling/identify/elevation-of-privlege/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/threat-modelling/identify/elevation-of-privlege/</guid>
				<description>&lt;h1 id=&#34;elevation-of-privlege&#34;&gt;Elevation of Privlege&lt;a class=&#34;anchor&#34; href=&#34;#elevation-of-privlege&#34;&gt;&lt;/a&gt;&lt;/h1&gt;&#xA;&lt;p&gt;Elevation of Privelege is a game created by Adam Shostack in which&lt;/p&gt;</description>
			</item>
			<item>
				<title>Brainstorming</title>
				<link>/docs/threat-modelling/identify/brainstorming/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>/docs/threat-modelling/identify/brainstorming/</guid>
				<description>&lt;h1 id=&#34;brainstorming&#34;&gt;Brainstorming&lt;a class=&#34;anchor&#34; href=&#34;#brainstorming&#34;&gt;&lt;/a&gt;&lt;/h1&gt;&#xA;&lt;p&gt;One of the most simple ways to identify threats is to host a brainstorming session. Brainstorming can be broken down into (1) a period of idea generation, and (2) a period of filtering where the best ideas are selected. Before brainstorming, it is often helpful to define the scope of attacks under consideration.&lt;/p&gt;&#xA;&lt;p&gt;On its own, brainstorming is not a sufficient form of threat modelling. This is because it is (deliberately) unstructured, and does not provide a high degree of confidence that all threats have been identified - i.e., did your brainstorming session end because you found all threats, or because you became tired / the meeting ended?&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
