<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jae Yoon Bae</title>
    <description>The latest articles on DEV Community by Jae Yoon Bae (@jae_yoon_bae).</description>
    <link>https://dev.to/jae_yoon_bae</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4182934%2F542d6b1c-f847-4905-9259-a53e3582fec7.png</url>
      <title>DEV Community: Jae Yoon Bae</title>
      <link>https://dev.to/jae_yoon_bae</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jae_yoon_bae"/>
    <language>en</language>
    <item>
      <title>Cloud Security Beyond Detection: Why Security State Transitions Matter</title>
      <dc:creator>Jae Yoon Bae</dc:creator>
      <pubDate>Tue, 13 Oct 2026 18:49:45 +0000</pubDate>
      <link>https://dev.to/jae_yoon_bae/cloud-security-beyond-detection-why-security-state-transitions-matter-10c4</link>
      <guid>https://dev.to/jae_yoon_bae/cloud-security-beyond-detection-why-security-state-transitions-matter-10c4</guid>
      <description>&lt;h1&gt;
  
  
  Cloud Security Beyond Detection: Why Security State Transitions Matter
&lt;/h1&gt;

&lt;p&gt;Cybersecurity is not just about detecting attacks. It's also about making sure systems recover securely after an incident.&lt;/p&gt;

&lt;p&gt;I'm currently working on a cybersecurity research project called &lt;strong&gt;Cybersecurity State Transition Integrity (CSTI)&lt;/strong&gt;, which focuses on verifying security state changes across interconnected systems.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;Traditional security tools can detect threats, monitor vulnerabilities, and identify compromised assets.&lt;/p&gt;

&lt;p&gt;But what happens during recovery?&lt;/p&gt;

&lt;p&gt;For example, a system might move through these states:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Compromised → Isolated → Cleaned → Reauthorized → Recovered&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Even if the system eventually reaches a secure state, an unsafe transition during recovery could introduce additional security risks.&lt;/p&gt;

&lt;h2&gt;
  
  
  My Approach
&lt;/h2&gt;

&lt;p&gt;With CSTI, I'm exploring how to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Track security state transitions across connected assets.&lt;/li&gt;
&lt;li&gt;Identify potentially unsafe recovery actions.&lt;/li&gt;
&lt;li&gt;Verify security policies before allowing transitions.&lt;/li&gt;
&lt;li&gt;Evaluate attack detection and recovery-policy effectiveness separately.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal is to improve security throughout the recovery process, rather than checking only the final state.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why This Matters for Cloud Security
&lt;/h2&gt;

&lt;p&gt;Cloud environments involve interconnected services, identities, applications, and resources.&lt;/p&gt;

&lt;p&gt;A security decision affecting one component can influence others. This makes it important to understand not only the security state of individual resources, but also how those states change.&lt;/p&gt;

&lt;p&gt;I believe security state transition verification could be useful for strengthening cloud incident recovery.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next?
&lt;/h2&gt;

&lt;p&gt;I'm continuing to develop and evaluate the CSTI prototype, focusing on reliability, detection performance, and secure recovery policies.&lt;/p&gt;

&lt;p&gt;I'm also interested in exploring how these ideas could be applied to cloud environments using technologies such as AWS.&lt;/p&gt;

&lt;p&gt;This is still a work in progress, and I'm looking forward to sharing what I learn along the way.&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>securityresearch</category>
      <category>cloudsecurity</category>
      <category>aws</category>
    </item>
  </channel>
</rss>
