<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Security-Controls on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/security-controls/</link>
		<description>Recent content in Security-Controls on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 17 Aug 2026 22:58:41 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/security-controls/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The CIA Triad Explained: Confidentiality, Integrity, and Availability</title>
				<link>https://www.compilemymind.com/posts/cia-triad-explained/</link>
				<pubDate>Mon, 17 Aug 2026 22:58:41 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/cia-triad-explained/</guid>
				<description>&lt;p&gt;The customer database is encrypted. Access requires a password and a second factor. The security team can point to both controls and say, correctly, that sensitive records are harder to steal.&lt;/p&gt;&#xA;&lt;p&gt;Then someone changes the bank account number on a supplier payment. On another morning, the application is unavailable when the finance team needs to stop that payment.&lt;/p&gt;&#xA;&lt;p&gt;Nothing in the word &lt;em&gt;encrypted&lt;/em&gt; answers either problem.&lt;/p&gt;&#xA;&lt;p&gt;That gap is why information security needs more than one goal. The &lt;strong&gt;CIA triad&lt;/strong&gt; divides the job into three outcomes: confidentiality, integrity, and availability. A secure system must keep information away from unauthorized people, protect it from unauthorized change or destruction, and make it usable by authorized people when they need it.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
