<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cybersecurity on Deployment</title><link>https://deployment.properties/tags/cybersecurity/</link><description>Recent content in cybersecurity on Deployment</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 16 Jul 2026 21:30:00 -0400</lastBuildDate><atom:link href="https://deployment.properties/tags/cybersecurity/index.xml" rel="self" type="application/rss+xml"/><item><title>The Abstraction Gap Between Security and Software Engineering</title><link>https://deployment.properties/posts/devsecops/the-abstraction-gap-between-security-and-software-engineering/</link><pubDate>Thu, 16 Jul 2026 21:30:00 -0400</pubDate><guid>https://deployment.properties/posts/devsecops/the-abstraction-gap-between-security-and-software-engineering/</guid><description>&lt;p>The other day, I was talking with some former software engineer teammates who are now at different companies, and the conversation turned to their relationships with their security teams. A familiar theme quickly emerged around the disconnect between security recommendations and the realities of their day-to-day engineering work. Sometimes it feels like we have come a long way as an industry, but many security teams still operate at a considerable distance from the engineers building and maintaining the systems they are trying to protect.&lt;/p></description></item></channel></rss>