<?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>Chillz Blog on Chillz Blog: SecEngAI, whatever...</title>
    <link>https://blog.chillz.work/</link>
    <description>Recent content in Chillz Blog on Chillz Blog: SecEngAI, whatever...</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Chillz Blog</copyright>
    <lastBuildDate>Sat, 02 May 2026 23:53:41 +0400</lastBuildDate>
    <atom:link href="https://blog.chillz.work/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Navigating Security Operations career path: talk alert🎤</title>
      <link>https://blog.chillz.work/posts/navigating-secops-path/</link>
      <pubDate>Sat, 02 May 2026 23:53:41 +0400</pubDate>
      <guid>https://blog.chillz.work/posts/navigating-secops-path/</guid>
      <description>&lt;p&gt;Hi! Recently I did a talk about Security Operations career path at Microsoft Innovation Center Armenia!🤓&lt;/p&gt;
&lt;h2 id=&#34;slides&#34;&gt;Slides📈&lt;/h2&gt;
&lt;p&gt;You can download the slides &lt;a href=&#34;https://blog.chillz.work/posts/navigating-secops-path/assets/Navigating%20SecOps.pdf&#34;&gt;here&lt;/a&gt; or watch in a widget below:&lt;/p&gt;

&lt;iframe class=&#34;speakerdeck-iframe&#34; frameborder=&#34;0&#34; src=&#34;https://speakerdeck.com/player/b3eed8032f7c447ca34321f4ee5ce369&#34; title=&#34;Navigating Security Operations career path&#34; allowfullscreen=&#34;true&#34; allow=&#34;web-share&#34; style=&#34;border: 0px; background: padding-box rgba(0, 0, 0, 0.1); margin: 0px; padding: 0px; border-radius: 6px; box-shadow: rgba(0, 0, 0, 0.2) 0px 5px 40px; width: 100%; height: auto; aspect-ratio: 560 / 315;&#34; data-ratio=&#34;1.7777777777777777&#34;&gt;&lt;/iframe&gt;


&lt;h2 id=&#34;short-agenda-of-my-talk&#34;&gt;Short agenda of my talk📝&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Intro to security teams responsibilities&lt;/li&gt;
&lt;li&gt;What does SecOps actually do?&lt;/li&gt;
&lt;li&gt;Big-Picture view on Security Operations Center process&lt;/li&gt;
&lt;li&gt;What is SIEM and detection engineering?&lt;/li&gt;
&lt;li&gt;How SecOps responds to threats: playbooks and automations&lt;/li&gt;
&lt;li&gt;Recovery methods&lt;/li&gt;
&lt;li&gt;How to obtain SecOps skills - useful resources and certifications‼️&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;bonus&#34;&gt;Bonus🎁&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;ve included a few practiacal cases in my presentation to make it less theoretical and out-of-context.
Read my presentation If you wonder how SQL-injections look from the defenders side!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hunting for diamonds💎: What is The Diamond Model?</title>
      <link>https://blog.chillz.work/posts/hunting-for-diamonds-part1/</link>
      <pubDate>Thu, 19 Mar 2026 13:43:10 +0400</pubDate>
      <guid>https://blog.chillz.work/posts/hunting-for-diamonds-part1/</guid>
      <description>&lt;p&gt;Hey! I am back with a new cycle of threat huting articles special for you. And in this part we are going to look into
the basics of &lt;a href=&#34;https://www.researchgate.net/publication/379381999_The_Diamond_Model_of_Intrusion_Analysis&#34;&gt;The Diamond Model&lt;/a&gt; of Intrusion Analysis and what it is about. I&amp;rsquo;ll try to keep it solely practical and simple.&lt;/p&gt;
&lt;p&gt;This thing is pretty popular in jobs requirements and is even implemented inside &lt;a href=&#34;https://github.com/OpenCTI-Platform/opencti&#34;&gt;OpenCTI Platform&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;Is this a real thing or yet another empty shell? Let&amp;rsquo;s dive in!&lt;/p&gt;</description>
    </item>
    <item>
      <title>New tool release! Welcome ycprox</title>
      <link>https://blog.chillz.work/posts/ycprox-release/</link>
      <pubDate>Sun, 04 Jan 2026 14:00:00 +0400</pubDate>
      <guid>https://blog.chillz.work/posts/ycprox-release/</guid>
      <description>&lt;p&gt;Hey! I recently developed a new tool &lt;a href=&#34;https://github.com/chlzen/ycprox/tree/main&#34;&gt;ycprox&lt;/a&gt; which allows you to quickly deploy a forward proxy in Yandex Cloud infrastructure to change your IP address (almost) each request.
You can check it out on Github and in this post I will cover some particularities I had to tackle / implement during development.&lt;/p&gt;
&lt;h2 id=&#34;the-idea&#34;&gt;The idea💡&lt;/h2&gt;
&lt;p&gt;Originally I wanted to adapt the existing &lt;a href=&#34;https://github.com/ustayready/fireprox/&#34;&gt;fireprox project&lt;/a&gt; for using Yandex Cloud (YC) resources. Here is how fireprox works in simple terms:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Policy 🆚 security alerts or why your SOC is suffering 😵</title>
      <link>https://blog.chillz.work/posts/policy-vs-security-alerts/</link>
      <pubDate>Mon, 23 Jun 2025 14:08:57 +0400</pubDate>
      <guid>https://blog.chillz.work/posts/policy-vs-security-alerts/</guid>
      <description>&lt;p&gt;Do you want to optimize your Mean Time To Response in your SOC? Do not feed your SOC with misconfigurations!&lt;/p&gt;
&lt;h1 id=&#34;whats-the-problem&#34;&gt;What&amp;rsquo;s the problem?🤔&lt;/h1&gt;
&lt;p&gt;You see, there are lots of alerts in your SIEM which your SOC analysts have nothing to do with.
Examples could be:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Unauthenticated service found&lt;/li&gt;
&lt;li&gt;Publicly available endpoint&lt;/li&gt;
&lt;li&gt;Password authentication on SSHD&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Security Operation Center is a great resource to find and contain threats, but very often SOC analysts encounter misconfiguration alerts which tell you only about probability of exploitation, not the malicious behaviour / threat has already occured.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to secure your AWS Lambda: talk alert!🎤</title>
      <link>https://blog.chillz.work/posts/securing-your-lambda-101-talk/</link>
      <pubDate>Sat, 14 Jun 2025 14:21:00 +0400</pubDate>
      <guid>https://blog.chillz.work/posts/securing-your-lambda-101-talk/</guid>
      <description>&lt;p&gt;Hey! Recently I&amp;rsquo;ve presented a talk at &lt;a href=&#34;https://www.linkedin.com/posts/cyhubarmenia_cyhubarmenia-securitybsides-bsides2025-activity-7339634074845650945--XKi?utm_source=share&amp;amp;utm_medium=member_desktop&amp;amp;rcm=ACoAAB2_NHkBDPG1E14quAQcaec2QAY_7hOThoo&#34;&gt;BSides Yerevan 2025&lt;/a&gt; about how to attack and defend your AWS Lambda serverless functions. This was my first attending of conference as a speaker and I am proud to be a part of invited speakers pool. Many thanks to &lt;a href=&#34;https://www.linkedin.com/company/cyhubarmenia&#34;&gt;CyHub Armenia&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;I would like to share my slides and demonstration I showed during my presentation. Don&amp;rsquo;t forget to mention me when using parts of my materials👀&lt;/p&gt;</description>
    </item>
    <item>
      <title>Authentication vs authorization in Zero Trust👀</title>
      <link>https://blog.chillz.work/posts/auth-vs-auth-zero-trust/</link>
      <pubDate>Tue, 27 May 2025 19:32:35 +0400</pubDate>
      <guid>https://blog.chillz.work/posts/auth-vs-auth-zero-trust/</guid>
      <description>&lt;h1 id=&#34;after-authentication-goes-authorization-right-wrong&#34;&gt;After authentication goes authorization, right? WRONG!❌&lt;/h1&gt;
&lt;p&gt;Well&amp;hellip; Not immediately. According to ZeroTrust methodologies, you have to dynamically make a decision of authorizing (or not) requests depending on state of your user / device / application and combinations of them🤔&lt;/p&gt;
&lt;p&gt;Think of authorization decision as a control plane &amp;ldquo;brain&amp;rdquo;, which instead of granting permissions right after authentication considers a few factors:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;device type: mobile / laptop&lt;/li&gt;
&lt;li&gt;location of device and / or user&lt;/li&gt;
&lt;li&gt;history of user-agents&lt;/li&gt;
&lt;li&gt;application access history of the user&lt;/li&gt;
&lt;li&gt;NAC-compliane of device&lt;/li&gt;
&lt;li&gt;etc&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;why&#34;&gt;Why&lt;/h2&gt;
&lt;p&gt;It makes your security less rigid than static policies, more flexible and context-rich. Also instead of simply denying request, you could ask for another auth-factor such as TOTP or SMS code.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AI usage policy👾</title>
      <link>https://blog.chillz.work/pages/ai-usage-policy/</link>
      <pubDate>Sat, 24 May 2025 19:01:39 +0400</pubDate>
      <guid>https://blog.chillz.work/pages/ai-usage-policy/</guid>
      <description>&lt;h2 id=&#34;about-using-llms-in-my-posts&#34;&gt;About using LLMs in my posts&lt;/h2&gt;
&lt;p&gt;Yeah, I know, everyone is using LLMs and me is not an exclusion, &lt;strong&gt;but&lt;/strong&gt;&amp;hellip;&lt;/p&gt;
&lt;p&gt;I think you would not be interested in reading this blog knowing that it was generated by ChatGPT — you can do it yourselves with carefully crafted prompt. And I do not want to make content only for content itself — I want to share with you cool new findings and knowledge I stubled upon intead of working on my blog popularity. For that purpose I have my &lt;a href=&#34;https://linkdedin.com/in/mogilin&#34;&gt;LinkedIn&lt;/a&gt;😄&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to: securely store passwords in DB🔐</title>
      <link>https://blog.chillz.work/posts/secure-password-store-db/</link>
      <pubDate>Mon, 19 May 2025 16:52:57 +0400</pubDate>
      <guid>https://blog.chillz.work/posts/secure-password-store-db/</guid>
      <description>&lt;p&gt;Wanna know how to securely store passwords in DB?&lt;/p&gt;
&lt;p&gt;There is a way to do it more securely than doing &lt;code&gt;SHA256(salt|password)&lt;/code&gt;. Recently I&amp;rsquo;ve read a &lt;a href=&#34;https://codahale.com/how-to-safely-store-a-password/&#34;&gt;great article about bcrypt&lt;/a&gt; and now I will definitely use it to hash passwords🔐&lt;/p&gt;
&lt;p&gt;The trick is in ability to control the complexity of hashing passwords so even in case of DB compromise the attackers will be significantly slowed down while brutefocing your hashed passwords👾&lt;/p&gt;
&lt;p&gt;Also your passwords will be prune to precomputed rainbow tables because all passwords have their own salt baked into password.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
