<?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>Dockerfile Linting Automation: Hadolint Rules Every Team Should Use</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Fri, 31 Jul 2026 07:16:52 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/dockerfile-linting-automation-hadolint-rules-every-team-should-use-5f9b</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/dockerfile-linting-automation-hadolint-rules-every-team-should-use-5f9b</guid>
      <description>&lt;p&gt;One un-pinned apt-get install line in a Dockerfile was all it took for a public-facing container image to ship a known-critical CVE for nine months. A linting rule that runs in under a second — before the image ever leaves the build machine — would have caught it on the first commit.&lt;/p&gt;

&lt;p&gt;Dockerfiles look deceptively simple: a dozen lines, a base image, a few RUN commands. But those lines encode every&lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/dockerfile-linting-automation-hadolint-rules-every-team-should-use" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/dockerfile-linting-automation-hadolint-rules-every-team-should-use&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/dockerfile-linting-automation-hadolint-rules-every-team-should-use" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>dockerfile</category>
      <category>hadolint</category>
      <category>linting</category>
      <category>cicd</category>
    </item>
    <item>
      <title>Threat Modeling for Microservices: A Practical Approach</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Wed, 29 Jul 2026 07:16:46 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/threat-modeling-for-microservices-a-practical-approach-43c1</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/threat-modeling-for-microservices-a-practical-approach-43c1</guid>
      <description>&lt;p&gt;In June 2025, a major fintech platform suffered a $2.3 million data breach when an attacker exploited an unauthenticated internal API between two microservices — an API that no one had documented, let alone threat-modeled. The service mesh was in place. The mTLS was configured. But the data flow between the payment service and the notification service was never reviewed, and a missing authorizatio&lt;/p&gt;

&lt;p&gt;👉 Read the full article with code examples and Arabic translation on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/threat-modeling-for-microservices-a-practical-approach" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/threat-modeling-for-microservices-a-practical-approach&lt;/a&gt;&lt;/p&gt;




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

</description>
      <category>threatmodeling</category>
      <category>microservices</category>
      <category>devsecops</category>
      <category>kubernetessecurity</category>
    </item>
    <item>
      <title>DevSecOps Pipeline Design: Embedding Security Gates in CI/CD</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Tue, 28 Jul 2026 07:15:47 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/devsecops-pipeline-design-embedding-security-gates-in-cicd-10l0</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/devsecops-pipeline-design-embedding-security-gates-in-cicd-10l0</guid>
      <description>&lt;p&gt;A single unpatched vulnerability in your CI/CD pipeline can compromise every artifact your team produces. In 2024, attackers exploited a misconfigured pipeline at a major cloud provider to inject malicious code into production builds — affecting over 23,000 customers before the breach was detected. These attacks aren't theoretical; they're the new frontier of software supply chain exploitation. Th&lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/devsecops-pipeline-design-embedding-security-gates-in-cicd" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/devsecops-pipeline-design-embedding-security-gates-in-cicd&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/devsecops-pipeline-design-embedding-security-gates-in-cicd" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>devsecops</category>
      <category>cicd</category>
      <category>pipelinesecurity</category>
      <category>securitygates</category>
    </item>
    <item>
      <title>Kubernetes Service Mesh Security: mTLS, Authorization, and Observability</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Sun, 26 Jul 2026 07:10:50 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/kubernetes-service-mesh-security-mtls-authorization-and-observability-508l</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/kubernetes-service-mesh-security-mtls-authorization-and-observability-508l</guid>
      <description>&lt;p&gt;In 2025, the average cost of a data breach reached $4.88 million according to IBM — but breaches involving compromised service mesh configurations cost an average of 30% more due to the lateral movement they enable. A misconfigured mTLS policy or overly permissive authorization rule in your service mesh can turn a single compromised pod into a cluster-wide catastrophe within seconds.&lt;/p&gt;

&lt;p&gt;As Kubernete&lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/kubernetes-service-mesh-security-mtls-authorization-and-observability" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/kubernetes-service-mesh-security-mtls-authorization-and-observability&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/kubernetes-service-mesh-security-mtls-authorization-and-observability" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>servicemesh</category>
      <category>mtls</category>
      <category>authorization</category>
    </item>
    <item>
      <title>Kubernetes Hardening: CIS Benchmarks and Runtime Protection</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Sat, 25 Jul 2026 07:08:31 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/kubernetes-hardening-cis-benchmarks-and-runtime-protection-3eje</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/kubernetes-hardening-cis-benchmarks-and-runtime-protection-3eje</guid>
      <description>&lt;p&gt;A single misconfigured Kubernetes cluster can expose thousands of containers to attackers within minutes. In 2025, the average Kubernetes cluster had 27 critical misconfigurations spanning RBAC, pod security, and network policies — and 68% of organizations reported at least one container-related security incident in production. Hardening your Kubernetes cluster against the CIS Benchmarks is not op&lt;/p&gt;

&lt;p&gt;👉 Read the full article on ShieldOps: &lt;a href="https://shieldops-ai.dev/blog/kubernetes-hardening-cis-benchmarks-and-runtime-protection" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/kubernetes-hardening-cis-benchmarks-and-runtime-protection&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/kubernetes-hardening-cis-benchmarks-and-runtime-protection" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>cisbenchmarks</category>
      <category>hardening</category>
      <category>runtimeprotection</category>
    </item>
    <item>
      <title>Kubernetes Ingress and API Gateway Security: TLS, Auth, and Rate Limiting</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Fri, 24 Jul 2026 07:16:35 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/kubernetes-ingress-and-api-gateway-security-tls-auth-and-rate-limiting-36hh</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/kubernetes-ingress-and-api-gateway-security-tls-auth-and-rate-limiting-36hh</guid>
      <description>&lt;p&gt;Your Kubernetes ingress is the front door to every service in your cluster — and most teams leave it unlocked, unmonitored, and wide open to attackers. A misconfigured Ingress controller or an API gateway with default settings can expose internal services to the internet, bypass authentication, and leak sensitive data through improperly terminated TLS.&lt;/p&gt;

&lt;p&gt;In the 2026 Cloud Native Security Survey by &lt;/p&gt;

&lt;p&gt;👉 Read the full article: &lt;a href="https://shieldops-ai.dev/blog/kubernetes-ingress-and-api-gateway-security-tls-auth-and-rate-limiting" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/kubernetes-ingress-and-api-gateway-security-tls-auth-and-rate-limiting&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/kubernetes-ingress-and-api-gateway-security-tls-auth-and-rate-limiting" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>ingress</category>
      <category>apigateway</category>
      <category>tls</category>
    </item>
    <item>
      <title>Kubernetes Audit Logging: Detecting Intrusions Through API Server Trails</title>
      <dc:creator>Mohammed Abdallah</dc:creator>
      <pubDate>Thu, 23 Jul 2026 07:17:20 +0000</pubDate>
      <link>https://dev.to/mohammed_abdallah_aef2d60/kubernetes-audit-logging-detecting-intrusions-through-api-server-trails-4om6</link>
      <guid>https://dev.to/mohammed_abdallah_aef2d60/kubernetes-audit-logging-detecting-intrusions-through-api-server-trails-4om6</guid>
      <description>&lt;p&gt;Every Kubernetes cluster leaves a digital fingerprint on every request that passes through its API server. Every kubectl apply, every pod creation, every Secret read — it is all recorded in the audit log. The problem? Most teams enable audit logging, archive the logs to object storage, and never inspect them until after a breach. By then, the audit trail is the only thing standing between your sec&lt;/p&gt;

&lt;p&gt;👉 Read the full article: &lt;a href="https://shieldops-ai.dev/blog/kubernetes-audit-logging:-detecting-intrusions-through-api-server-trails" rel="noopener noreferrer"&gt;https://shieldops-ai.dev/blog/kubernetes-audit-logging:-detecting-intrusions-through-api-server-trails&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://shieldops-ai.dev/blog/kubernetes-audit-logging:-detecting-intrusions-through-api-server-trails" rel="noopener noreferrer"&gt;ShieldOps Blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>auditlogging</category>
      <category>intrusiondetection</category>
      <category>apiserver</category>
    </item>
    <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>
  </channel>
</rss>
