<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Confidentiality on Rietta Cybersecurity</title>
    <link>https://rietta.com/glossary/confidentiality/</link>
    <description>Recent content in Confidentiality on Rietta Cybersecurity</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>1999-2026 Rietta Inc. All Rights Reserved.</copyright>
    <lastBuildDate>Sun, 27 Sep 2026 16:10:44 -0400</lastBuildDate>
    <atom:link href="https://rietta.com/glossary/confidentiality/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Five Pillars of Information Security (And Why We Audit Accessibility)</title>
      <link>https://rietta.com/blog/five-pillars-infosec-ada-accessibility/</link>
      <pubDate>Sat, 25 Jul 2026 15:00:00 +0000</pubDate>
      <guid>https://rietta.com/blog/five-pillars-infosec-ada-accessibility/</guid>
      <description>Rietta is a cybersecurity firm. So why have the last three posts on this blog been about missing document titles, undefined languages, and metadata fields in government PDFs? My reasoning comes down to this: accessibility failures are security failures, specifically, they&amp;rsquo;re availability failures, and detecting them at scale is exactly the discipline our industry already practices.&#xA;To explain why, it helps to back up and lay out the actual model we use to reason about security in the first place.</description>
    </item>
  </channel>
</rss>
