<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Audit on Andrew Sheves</title><link>https://andrewsheves.com/tags/audit/</link><description>Recent content in Audit on Andrew Sheves</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 24 Feb 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://andrewsheves.com/tags/audit/index.xml" rel="self" type="application/rss+xml"/><item><title>Using blockchain to validate records in DCDR</title><link>https://andrewsheves.com/2021/02/24/using-blockchain-to-validate-records-in-dcdr/</link><pubDate>Wed, 24 Feb 2021 00:00:00 +0000</pubDate><guid>https://andrewsheves.com/2021/02/24/using-blockchain-to-validate-records-in-dcdr/</guid><description>&lt;p&gt;Security is a guiding principle for DCDR, and protecting user data has been baked in from the start. However, there’s more to data security than restricting access and managing user permissions. I’ve used the INFOSEC abbreviation CIA – &lt;em&gt;confidentiality, integrity, and availability&lt;/em&gt; – as a guide to help determine the steps required to protect your data while also ensuring that the system does what it’s supposed to. Overall, the intent is to ensure:&lt;/p&gt;</description></item></channel></rss>