<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Daniel Ancuta</title><link>https://ancuta.org/tags/security/</link><description>Recent content in Security on Daniel Ancuta</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Daniel Ancuta</copyright><lastBuildDate>Sun, 01 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ancuta.org/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Agents in Your CI/CD: Why GitHub Rulesets Matter Now More Than Ever</title><link>https://ancuta.org/posts/ai-agents-in-your-ci-cd-why-github-rulesets-matter/</link><pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate><guid>https://ancuta.org/posts/ai-agents-in-your-ci-cd-why-github-rulesets-matter/</guid><description>&lt;p&gt;AI agents are getting scary good. Tools like &lt;a href="https://github.com/anthropics/clawbot" target="_blank" rel="noreferrer"&gt;clawbot&lt;/a&gt; can understand your codebase, write features, fix bugs, and commit changes - all without much human input.&lt;/p&gt;&#10;&lt;p&gt;But that doesn&amp;rsquo;t mean you should let them run wild.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://ancuta.org/posts/ai-agents-in-your-ci-cd-why-github-rulesets-matter/featured.jpg"/></item><item><title>Protect Sensitive Data in Logs with AWS CloudWatch Data Masking</title><link>https://ancuta.org/posts/protect-sensitive-data-in-logs-with-aws-cloudwatch-data-masking/</link><pubDate>Wed, 12 Mar 2025 00:00:00 +0000</pubDate><guid>https://ancuta.org/posts/protect-sensitive-data-in-logs-with-aws-cloudwatch-data-masking/</guid><description>&lt;p&gt;Logging is part of every application, at least they should, but often logs contain sensitive information.&lt;/p&gt;&#10;&lt;p&gt;PII (Personally Identifiable Information), PHI (Protected Health Information), and other confidential data often &lt;strong&gt;end up in logs&lt;/strong&gt; - often unintentionally.&#10;Storing &lt;strong&gt;raw, unmasked logs&lt;/strong&gt; can lead to &lt;strong&gt;compliance violations (GDPR, HIPAA, SOC 2)&lt;/strong&gt;, security risks, and &lt;strong&gt;data exposure&lt;/strong&gt; if logs are misused.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://ancuta.org/posts/protect-sensitive-data-in-logs-with-aws-cloudwatch-data-masking/featured.png"/></item><item><title>GitHub Actions: Security Hardening With OpenID Connect</title><link>https://ancuta.org/posts/github-actions-security-hardening-with-openid-connect/</link><pubDate>Thu, 06 Mar 2025 00:00:00 +0000</pubDate><guid>https://ancuta.org/posts/github-actions-security-hardening-with-openid-connect/</guid><description>&lt;p&gt;The easiest way to configure your CI/CD pipeline with AWS is to just create long-lived credentials, access and secret key, and store them in GitHub Actions.&lt;/p&gt;&#10;&lt;p&gt;While this method works, it has &lt;strong&gt;several security risks&lt;/strong&gt;:&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://ancuta.org/posts/github-actions-security-hardening-with-openid-connect/featured.jpg"/></item><item><title>Secrets Management in AWS: Using Secrets Manager</title><link>https://ancuta.org/posts/secrets-management-in-aws-using-secrets-manager-for-your-microservices/</link><pubDate>Sat, 01 Mar 2025 00:00:00 +0000</pubDate><guid>https://ancuta.org/posts/secrets-management-in-aws-using-secrets-manager-for-your-microservices/</guid><description>&lt;p&gt;Sharing secrets across microservices creates security risks. Not only when one of the microservices is compromised, as then during rotation of single secret all of your microservices will be affected. Leading to potential downtimes.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://ancuta.org/posts/secrets-management-in-aws-using-secrets-manager-for-your-microservices/featured.jpg"/></item></channel></rss>