<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Austin Krauza</title>
    <link>https://blog.krauza.com/posts/</link>
    <description>Recent content in Posts on Austin Krauza</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 09 May 2022 00:00:00 +0000</lastBuildDate>
    
        <atom:link href="https://blog.krauza.com/posts/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>About</title>
      <link>https://blog.krauza.com/about/</link>
      <pubDate>Mon, 09 May 2022 00:00:00 +0000</pubDate>
      
      <guid>https://blog.krauza.com/about/</guid>
      <description>Austin Krauza is a Site Reliability Engineer for Identity and Trust Platforms at JPMorgan Chase &amp;amp; Co. Previously, Austin has worked a SRE building out the monitoring of the Private Cloud environment, and as a Platform Engineer building several internal platforms for the firm. He graduated from the Honors College of the City University of New York (CUNY) in June 2016 with a Bachelors of Science in Computer Science, and is currently pursuing a Masters of Science in Cybersecurity from New York University.</description>
    </item>
    
    <item>
      <title>SLOConf 2022: What are SLI&#39;s, and why should I care?</title>
      <link>https://blog.krauza.com/2022/05/sloconf_2022/</link>
      <pubDate>Mon, 09 May 2022 00:00:00 +0000</pubDate>
      
      <guid>https://blog.krauza.com/2022/05/sloconf_2022/</guid>
      <description>Introduction Every day we interact with a variety of systems both online and offline – from our visit to the bagel store to checking our email on mobile. Very commonly within the Reliability Engineering community we talk about Service Level Objectives (SLO’s), but rarely do we talk about the underpinning indicators that tell us whether a system is healthy. Typically, engineers begin picking the low hanging fruit objectives (such as request time and volume), rather than doing a full analysis of their dependencies and the metrics which are available to them from their systems or application.</description>
    </item>
    
    <item>
      <title>Signed SSH Certificates</title>
      <link>https://blog.krauza.com/2022/05/ssh_certificates/</link>
      <pubDate>Sun, 08 May 2022 00:00:00 +0000</pubDate>
      
      <guid>https://blog.krauza.com/2022/05/ssh_certificates/</guid>
      <description>(This work was completed as part of my participation in NYU Course CS GY 6813: Information Security &amp;amp; Privacy)
Introduction SSH (Secure Shell) key pairs are one of the most secure ways to authenticate to a system when using the SSH protocol. When accessing a system, traditionally users would authenticate using a username and password combination, which only provides one factor authentication (something you know). If a user’s credentials were obtained and used by a bad actor (through a phishing attempt, credential dump, password crack, etc.</description>
    </item>
    
  </channel>
</rss>
