<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Threat-Modeling on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/threat-modeling/</link>
		<description>Recent content in Threat-Modeling on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 26 May 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/threat-modeling/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Security Is an Architecture Concern</title>
				<link>https://dplabs.tech/blog/security-is-architecture-concern/</link>
				<pubDate>Mon, 26 May 2025 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/security-is-architecture-concern/</guid>
				<description>&lt;p&gt;Security gets treated as a feature set: authentication, authorization, input validation, encryption. Implement those features and the system is secure. This framing is wrong and produces systems that are secure in obvious ways while vulnerable in non-obvious ones.&lt;/p&gt;&#xA;&lt;p&gt;Security is an emergent property of architectural decisions: where trust boundaries are placed, how data flows between components, what permissions components have, how failures are handled. These decisions are made during design, not during a security review at the end.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
