<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Non-Repudiation on Rietta Cybersecurity</title>
    <link>https://rietta.com/glossary/non-repudiation/</link>
    <description>Recent content in Non-Repudiation 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/non-repudiation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Non-Repudiation in Cybersecurity</title>
      <link>https://rietta.com/blog/non-repudiation/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://rietta.com/blog/non-repudiation/</guid>
      <description>Non-repudiation is the among the five foundational security properties in the five pillars of information assurance, CIANA (a superset of the CIA Triad):&#xA;Confidentiality Integrity Availability Non-repudiation Authentication [&amp;amp; Access Control] In my lecture content, I often call this the one of the &amp;ldquo;log more things&amp;rdquo; properties. The idea is to log the who, what, when, and where access occurs. When properly implemented a non-repudiation control should allow you to not only know who did an action but also prove that another party did not do it instead.</description>
    </item>
    <item>
      <title>On Flock Cameras and &#34;What Do You Have to Hide&#34;</title>
      <link>https://rietta.com/blog/on-flock-cameras/</link>
      <pubDate>Tue, 15 Sep 2026 10:00:00 -0400</pubDate>
      <guid>https://rietta.com/blog/on-flock-cameras/</guid>
      <description>The following is my personal opinion, based on published media reporting about automated license plate reader (ALPR) systems generally and Flock Safety specifically. I have no insider knowledge of Flock&amp;rsquo;s systems, architecture, or operations.&#xA;You want to be very careful with any &amp;ldquo;what do you have to hide&amp;rdquo; argument. That&amp;rsquo;s a fast slippery slope to tyranny. The value has to be balanced against the risks and the protection of civil liberties.</description>
    </item>
    <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>
