<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hadoop on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/categories/hadoop/</link>
    <description>Recent content in Hadoop on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 12 Sep 2020 22:01:52 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/categories/hadoop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enforcing a least privileged security model can be hard</title>
      <link>https://ronaldbradford.com/blog/enforcing-a-least-privileged-security-model-can-be-hard-2020-09-12/</link>
      <pubDate>Sat, 12 Sep 2020 22:01:52 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/enforcing-a-least-privileged-security-model-can-be-hard-2020-09-12/</guid>
      <description>In a greenfield environment you generally have the luxury to right any wrongs of any past tech debt. It can be more difficult to apply this to an existing environment? For example, my setup is configured to just work with the AWS CLI and various litmus tests to validate that.</description>
    </item>
  </channel>
</rss>
