<?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: Mohammed Abdallah</title>
    <description>The latest articles on DEV Community by Mohammed Abdallah (@mohammed_abdallah_aef2d60).</description>
    <link>https://dev.to/mohammed_abdallah_aef2d60</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%2F3611549%2Ff778e600-aa1f-4a4f-8179-0563a7b3400e.jpg</url>
      <title>DEV Community: Mohammed Abdallah</title>
      <link>https://dev.to/mohammed_abdallah_aef2d60</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mohammed_abdallah_aef2d60"/>
    <language>en</language>
    <item>
      <title>The DevSecOps Dictionary: 25 Terms Every Developer Should Know</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Sun, 19 Jul 2026 07:09:30 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/the-devsecops-dictionary-25-terms-every-developer-should-know-40m1</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/the-devsecops-dictionary-25-terms-every-developer-should-know-40m1</guid>
      <description>&lt;p&gt;DevSecOps is full of jargon. Every day, security engineers throw around terms like "SBOM," "Shift Left," "CVE," "Policy as Code," and "Admission Controller" — and if you're new to the field, it can feel like a foreign language. But understanding these 25 terms isn't just about sounding knowledgeable in meetings; it's about being able to read security reports, configure CI/CD pipelines, and protect\n\n👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/the-devsecops-dictionary:-25-terms-every-developer-should-know%5Cn%5Cn---%5Cn%5Cn*Originally" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/the-devsecops-dictionary:-25-terms-every-developer-should-know\n\n---\n\n*Originally&lt;/a&gt; published on &lt;a href="https://shieldops-ai.dev/blog/the-devsecops-dictionary:-25-terms-every-developer-should-know" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.*&lt;/p&gt;

</description>
      <category>devsecops</category>
      <category>dictionary</category>
      <category>glossary</category>
      <category>containersecurity</category>
    </item>
    <item>
      <title>Your First Security Scan: A Step-by-Step Guide With ShieldOps</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Sat, 18 Jul 2026 07:08:30 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/your-first-security-scan-a-step-by-step-guide-with-shieldops-38i</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/your-first-security-scan-a-step-by-step-guide-with-shieldops-38i</guid>
      <description>&lt;p&gt;You have built your first Docker container, deployed it to a test server, and everything runs beautifully. But here is the uncomfortable truth: your container almost certainly contains vulnerabilities you did not intend to ship. A single docker pull on an outdated base image can pull in fifty known CVEs before you write a single line of application code. The gap between "it works" and "it is secur&lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/your-first-security-scan-a-step-by-step-guide-with-shieldops" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/your-first-security-scan-a-step-by-step-guide-with-shieldops&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/your-first-security-scan-a-step-by-step-guide-with-shieldops" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>securityscan</category>
      <category>trivy</category>
      <category>shieldops</category>
      <category>containersecurity</category>
    </item>
    <item>
      <title>Docker vs Kubernetes Security: What Beginners Need to Know</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Fri, 17 Jul 2026 07:12:27 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/docker-vs-kubernetes-security-what-beginners-need-to-know-fbb</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/docker-vs-kubernetes-security-what-beginners-need-to-know-fbb</guid>
      <description>&lt;p&gt;If you are new to container security, the first question you will hear is: Docker or Kubernetes? But that is the wrong question. The real question is how each platform approaches security, what threats each model addresses, and — most importantly — how they complement each other when used together. Docker secures the container build and runtime on a single host. Kubernetes secures a distributed cl&lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/docker-vs-kubernetes-security-what-beginners-need-to-know" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/docker-vs-kubernetes-security-what-beginners-need-to-know&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/docker-vs-kubernetes-security-what-beginners-need-to-know" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>kubernetes</category>
      <category>containersecurity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Understanding CVEs: How Vulnerability Databases Protect Your Software</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Thu, 16 Jul 2026 07:19:26 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/understanding-cves-how-vulnerability-databases-protect-your-software-23l</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/understanding-cves-how-vulnerability-databases-protect-your-software-23l</guid>
      <description>&lt;p&gt;Every week, more than 200 new vulnerabilities are published to the National Vulnerability Database — and that number keeps rising. In 2025 alone, over 40,000 CVEs were disclosed, a 30% increase from the previous year. If your team is still treating every CVE with the same urgency — or worse, ignoring the flood entirely — you are either wasting engineering time on noise or leaving your containerize&lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/understanding-cves-how-vulnerability-databases-protect-your-software" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/understanding-cves-how-vulnerability-databases-protect-your-software&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/understanding-cves-how-vulnerability-databases-protect-your-software" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>cve</category>
      <category>vulnerabilitydatabase</category>
      <category>cvss</category>
      <category>epss</category>
    </item>
    <item>
      <title>What Is Container Security? A Beginner's Guide to Docker Safety</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Wed, 15 Jul 2026 07:14:25 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/what-is-container-security-a-beginners-guide-to-docker-safety-2gf0</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/what-is-container-security-a-beginners-guide-to-docker-safety-2gf0</guid>
      <description>&lt;p&gt;You've heard about containers. You're using Docker. You know they make deployment fast and reliable. But there's a question few people answer honestly: do you actually know how to secure them? If your answer is "not really," you're not alone — and this guide is for you.&lt;br&gt;
Container security is the practice of protecting containerized applications — from the base image you start with, to the runtime &lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/what-is-container-security-a-beginners-guide-to-docker-safety" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/what-is-container-security-a-beginners-guide-to-docker-safety&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/what-is-container-security-a-beginners-guide-to-docker-safety" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>containersecurity</category>
      <category>docker</category>
      <category>beginners</category>
      <category>securitybasics</category>
    </item>
    <item>
      <title>Weekly Security Hygiene: A 15-Minute Checklist for Container Teams</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Tue, 14 Jul 2026 07:14:41 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/weekly-security-hygiene-a-15-minute-checklist-for-container-teams-20a3</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/weekly-security-hygiene-a-15-minute-checklist-for-container-teams-20a3</guid>
      <description>&lt;p&gt;You ran three critical CVEs in production for two weeks because the vulnerability report landed in your inbox on a Friday and you forgot to check it by Monday. A developer accidentally pushed a .env file to a public repository, and nobody noticed until the security scanner flagged it — three days later. A container running with --privileged flags has been quietly scraping secrets from neighboring &lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/weekly-security-hygiene-a-15-minute-checklist-for-container-teams" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/weekly-security-hygiene-a-15-minute-checklist-for-container-teams&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/weekly-security-hygiene-a-15-minute-checklist-for-container-teams" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>containersecurity</category>
      <category>securityhygiene</category>
      <category>weeklychecklist</category>
      <category>devsecops</category>
    </item>
    <item>
      <title>Shell Command Security: 10 Dangerous Patterns in Dockerfiles and How to Fix Them</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Mon, 13 Jul 2026 07:16:20 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/shell-command-security-10-dangerous-patterns-in-dockerfiles-and-how-to-fix-them-3dda</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/shell-command-security-10-dangerous-patterns-in-dockerfiles-and-how-to-fix-them-3dda</guid>
      <description>&lt;p&gt;Did you know that a single curl | bash command in your Dockerfile can bypass every signature verification, integrity check, and security control you've painstakingly configured? Shell commands are the most executed — yet most overlooked — attack surface in container builds. One unvalidated pipe, one unescaped variable, and your hardened image ships with a backdoor.&lt;/p&gt;

&lt;p&gt;In 2025, the NorthStar malware &lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/shell-command-security-10-dangerous-patterns-in-dockerfiles-and-how-to-fix-them" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/shell-command-security-10-dangerous-patterns-in-dockerfiles-and-how-to-fix-them&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/shell-command-security-10-dangerous-patterns-in-dockerfiles-and-how-to-fix-them" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>shellsecurity</category>
      <category>dockerfile</category>
      <category>dockersecurity</category>
      <category>supplychain</category>
    </item>
    <item>
      <title>4 Kubernetes Annotations That Instantly Improve Your Security Posture</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Sun, 12 Jul 2026 07:07:05 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/4-kubernetes-annotations-that-instantly-improve-your-security-posture-jbc</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/4-kubernetes-annotations-that-instantly-improve-your-security-posture-jbc</guid>
      <description>&lt;p&gt;Most Kubernetes teams focus on RBAC, network policies, and pod security contexts — and they should. But there is a set of battle-tested Kubernetes annotations that can instantly harden your cluster's security posture with minimal effort. These annotations control everything from syscall filtering to ingress encryption, and most clusters run without them.&lt;/p&gt;

&lt;p&gt;Kubernetes annotations are key-value metad&lt;/p&gt;

&lt;p&gt;👉 Read the full article: &lt;a href="https://shieldops-ai.dev/blog/4-kubernetes-annotations-that-instantly-improve-your-security-posture" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/4-kubernetes-annotations-that-instantly-improve-your-security-posture&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/4-kubernetes-annotations-that-instantly-improve-your-security-posture" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>annotations</category>
      <category>podsecurity</category>
      <category>seccomp</category>
    </item>
    <item>
      <title>Docker Bridge Network Security: One Setting That Changes Everything</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Sat, 11 Jul 2026 07:07:50 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/docker-bridge-network-security-one-setting-that-changes-everything-7bg</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/docker-bridge-network-security-one-setting-that-changes-everything-7bg</guid>
      <description>&lt;p&gt;Your Docker containers are wide open to each other by default. The docker0 bridge lets every container on the same host communicate with every other container — no firewall, no authentication, no questions asked. One compromised container becomes a launchpad for lateral movement across your entire host. But a single daemon setting changes everything.&lt;/p&gt;

&lt;p&gt;Docker's default bridge network is the most ov\n\n👉 Read the full article: &lt;a href="https://shieldops-ai.dev/blog/docker-bridge-network-security-one-setting-that-changes-everything%5Cn%5Cn---%5Cn%5Cn*Originally" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/docker-bridge-network-security-one-setting-that-changes-everything\n\n---\n\n*Originally&lt;/a&gt; published on &lt;a href="https://shieldops-ai.dev/blog/docker-bridge-network-security-one-setting-that-changes-everything" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.*&lt;/p&gt;

</description>
      <category>docker</category>
      <category>bridgenetwork</category>
      <category>networksecurity</category>
      <category>containerisolation</category>
    </item>
    <item>
      <title>Container Vulnerability Triage: Separating Real Threats From Noise</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Fri, 10 Jul 2026 07:18:49 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/container-vulnerability-triage-separating-real-threats-from-noise-341k</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/container-vulnerability-triage-separating-real-threats-from-noise-341k</guid>
      <description>&lt;p&gt;A development team runs Trivy against a container image and gets back 847 CVEs — 23 critical, 91 high, 342 medium, 391 low. Panic sets in. The security team demands every critical CVE be fixed before deployment. The engineering lead pushes back: "We can't delay the release for false positives." The argument escalates. The deployment stalls. Meanwhile, attackers are actively exploiting just 3 of th&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;Read the full article with code examples, Arabic translation, and interactive FAQ on ShieldOps:&lt;/strong&gt; &lt;a href="https://shieldops-ai.dev/blog/container-vulnerability-triage-separating-real-threats-from-noise" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/container-vulnerability-triage-separating-real-threats-from-noise&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>vulnerability</category>
      <category>triage</category>
      <category>cvss</category>
      <category>epss</category>
    </item>
    <item>
      <title>Top 10 kubectl Plugins for Security Engineers in 2026</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Thu, 09 Jul 2026 07:16:56 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/top-10-kubectl-plugins-for-security-engineers-in-2026-101g</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/top-10-kubectl-plugins-for-security-engineers-in-2026-101g</guid>
      <description>&lt;p&gt;Your kubectl is a Swiss Army knife — but it's missing the security blades. Kubernetes clusters grow more complex every quarter, and the default kubectl commands simply weren't designed for deep security analysis. In 2026, a Kubernetes security engineer needs more than kubectl get pods and kubectl describe. You need plugins that sniff network traffic on running containers, map RBAC permissions visu&lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/top-10-kubectl-plugins-for-security-engineers-in-2026" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/top-10-kubectl-plugins-for-security-engineers-in-2026&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/top-10-kubectl-plugins-for-security-engineers-in-2026" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubectl</category>
      <category>kubernetes</category>
      <category>security</category>
      <category>plugins</category>
    </item>
    <item>
      <title>Docker Image Size Reduction: 8 Techniques That Also Improve Security</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Wed, 08 Jul 2026 07:16:03 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/docker-image-size-reduction-8-techniques-that-also-improve-security-lac</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/docker-image-size-reduction-8-techniques-that-also-improve-security-lac</guid>
      <description>&lt;p&gt;A 500 MB Docker image doesn't just slow your CI/CD pipeline — it multiplies your attack surface by hundreds of packages, thousands of CVEs, and dozens of unnecessary binaries that attackers love to exploit. Every megabyte you strip from your container image is a potential vulnerability you never have to patch.&lt;/p&gt;

&lt;p&gt;Docker image size isn't just a performance concern. Bloated images carry unused package&lt;/p&gt;

&lt;p&gt;👉 Read the full article with code examples and Arabic translation: &lt;a href="https://shieldops-ai.dev/blog/docker-image-size-reduction-8-techniques-that-also-improve-security" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/docker-image-size-reduction-8-techniques-that-also-improve-security&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/docker-image-size-reduction-8-techniques-that-also-improve-security" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>imagesize</category>
      <category>containersecurity</category>
      <category>devsecops</category>
    </item>
  </channel>
</rss>
