<?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 Abdelbaki Ben Elhaj Slimene</title><link>https://bakic.github.io/tags/security/</link><description>Recent content in Security on Abdelbaki Ben Elhaj Slimene</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bakic.github.io/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Making 'Nothing Leaves Your Browser' a Promise the Browser Enforces</title><link>https://bakic.github.io/posts/csp-privacy-client-side-developer-tools/</link><pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate><guid>https://bakic.github.io/posts/csp-privacy-client-side-developer-tools/</guid><description>&lt;p&gt;Developers paste things into online tools that they would never put in a public chat: a JWT from staging, a JSON payload with customer data, a connection string with the password still in it. Every &amp;ldquo;format your JSON online&amp;rdquo; site says it doesn&amp;rsquo;t store what you paste. Almost none of them can prove it, and you can&amp;rsquo;t tell the difference between a site that doesn&amp;rsquo;t upload your input and a site that just says so.&lt;/p&gt;</description></item><item><title>Migrating from SMTP to AWS SES with IAM Roles: A Security-First Approach to Email in Spring Boot</title><link>https://bakic.github.io/posts/smtp-to-aws-ses-iam-roles-spring-boot/</link><pubDate>Wed, 28 Jan 2026 00:00:00 +0000</pubDate><guid>https://bakic.github.io/posts/smtp-to-aws-ses-iam-roles-spring-boot/</guid><description>&lt;p&gt;Sending emails is a fundamental requirement for most applications. Whether it’s transactional notifications, alerts, or user communications, we need a reliable and secure way to dispatch messages.&lt;/p&gt;&#10;&lt;p&gt;In this article, I’ll walk through our migration from traditional SMTP authentication to AWS SES with IAM role-based authentication, explaining why this shift represents a significant security improvement.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="image-1.jpg" alt="Photo by CHUTTERSNAP on Unsplash"&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;Photo by &lt;a href="https://unsplash.com/@chuttersnap?utm_source=medium&amp;amp;utm_medium=referral"&gt;CHUTTERSNAP&lt;/a&gt; on &lt;a href="https://unsplash.com?utm_source=medium&amp;amp;utm_medium=referral"&gt;Unsplash&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;&#10;&lt;h2 id="the-traditional-approach-smtp-with-credentials"&gt;The Traditional Approach: SMTP with Credentials&lt;/h2&gt;&#10;&lt;p&gt;For years, the standard way to send emails from a Spring Boot application has been through SMTP with username and password authentication:&lt;/p&gt;</description></item><item><title>Presigned URLs in AWS S3: Secure File Upload and Download</title><link>https://bakic.github.io/posts/presigned-urls-aws-s3/</link><pubDate>Mon, 09 Oct 2023 00:00:00 +0000</pubDate><guid>https://bakic.github.io/posts/presigned-urls-aws-s3/</guid><description>&lt;p&gt;Amazon Simple Storage Service (S3) is an object storage service offered by Amazon Web Services (AWS). It allows users to store and retrieve data from anywhere on the web. While you can manage S3 objects directly through the AWS Management Console and the AWS SDKs with dedicated permissions, there are situations where you need to securely grant temporary access to your S3 objects without exposing your AWS credentials. This is where presigned URLs come into play.&lt;/p&gt;</description></item></channel></rss>