<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>securecode.dev</title><link>https://securecode.dev/</link><description>Recent content on securecode.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://securecode.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Security</title><link>https://securecode.dev/services/ai-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://securecode.dev/services/ai-security/</guid><description>&lt;p>Modern AI products inherit traditional application risk and add new failure modes around model behavior, data handling, tool access, agent autonomy, and user-generated input. Effective AI security work has to account for all of them together.&lt;/p></description></item><item><title>Security Practices</title><link>https://securecode.dev/services/product-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://securecode.dev/services/product-security/</guid><description>&lt;p>Security practices are most effective when they are embedded close to architecture and delivery, not treated as an isolated compliance function. The goal is to help teams build secure defaults into the product lifecycle while keeping engineering momentum intact.&lt;/p></description></item><item><title>Penetration Testing</title><link>https://securecode.dev/services/penetration-testing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://securecode.dev/services/penetration-testing/</guid><description>&lt;p>Penetration testing should do more than produce a list of issues. The most useful assessments help teams understand exploit paths, validate assumptions, and decide what to fix first.&lt;/p></description></item><item><title>Security Automation</title><link>https://securecode.dev/services/security-automation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://securecode.dev/services/security-automation/</guid><description>&lt;p>Security work scales best when repetitive checks, handoffs, and reporting loops are codified. Automation should reduce noise, improve consistency, and put useful feedback where engineers already work.&lt;/p></description></item><item><title>Vulnerability Management</title><link>https://securecode.dev/services/vulnerability-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://securecode.dev/services/vulnerability-management/</guid><description>&lt;p>Many teams already have security data. The harder problem is turning it into useful operating decisions. Vulnerability management should connect technical findings to ownership, risk context, remediation planning, and leadership visibility.&lt;/p></description></item><item><title>AI Security Risks in SaaS Platforms</title><link>https://securecode.dev/insights/ai-security-risks-in-saas-platforms/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/ai-security-risks-in-saas-platforms/</guid><description>&lt;p>AI-enabled SaaS features often get reviewed as isolated prompts or model calls, but the meaningful risk usually sits in the surrounding application workflow. Permissions, tenant boundaries, tool execution, retrieval pipelines, and output handling all matter more than the model alone.&lt;/p></description></item><item><title>Threat Modeling Modern APIs</title><link>https://securecode.dev/insights/threat-modeling-modern-apis/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/threat-modeling-modern-apis/</guid><description>&lt;p>Threat modeling APIs is often reduced to a short checklist around authentication and transport security. That rarely surfaces the issues that matter most. Real API risk tends to come from workflow design, trust assumptions between services, and weak authorization at object or action boundaries.&lt;/p></description></item><item><title>Building Security Into CI/CD</title><link>https://securecode.dev/insights/building-security-into-ci/cd/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/building-security-into-ci/cd/</guid><description>&lt;p>Security controls in CI/CD often fail for one of two reasons: they trigger too late to be useful, or they create enough noise that teams stop trusting them. Good pipeline security design is less about adding more scanners and more about deciding where feedback belongs.&lt;/p></description></item><item><title>Secure AI Integration Patterns</title><link>https://securecode.dev/insights/secure-ai-integration-patterns/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/secure-ai-integration-patterns/</guid><description>&lt;p>The safest AI integrations do not rely on the model to be correct, aligned, or cautious. They assume the model can be manipulated, can hallucinate, and can generate plausible but unsafe output. The surrounding system is what turns those limitations into manageable engineering risk.&lt;/p></description></item><item><title>Practical Product Security Reviews</title><link>https://securecode.dev/insights/practical-product-security-reviews/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/practical-product-security-reviews/</guid><description>&lt;p>Product security reviews are easy to make expensive and hard to make useful. A review that produces a long list of generic best practices may look thorough while still failing to help the team make better decisions.&lt;/p></description></item><item><title>About</title><link>https://securecode.dev/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://securecode.dev/about/</guid><description>&lt;p>securecode.dev is built around a simple belief: strong security work should improve engineering quality, decision-making, and delivery confidence.&lt;/p>
&lt;h2 id="engineering-first-philosophy">Engineering-first philosophy&lt;/h2>
&lt;p>Security recommendations are most useful when they are grounded in system design, deployment patterns, developer workflows, and the way modern teams actually ship software. That means the work stays technical, contextual, and practical.&lt;/p></description></item><item><title>Contact</title><link>https://securecode.dev/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://securecode.dev/contact/</guid><description>&lt;p>If you are planning an assessment, need a technical security partner, or want to improve security practices across engineering, get in touch.&lt;/p></description></item><item><title>Privacy Policy</title><link>https://securecode.dev/privacy-policy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://securecode.dev/privacy-policy/</guid><description>&lt;p>This Privacy Policy describes how securecode.dev collects and uses information through this website.&lt;/p>
&lt;h2 id="information-collected">Information collected&lt;/h2>
&lt;p>If you submit an inquiry, the information you provide may include your name, email address, company, project details, and any other information you choose to share.&lt;/p></description></item><item><title>Terms</title><link>https://securecode.dev/terms/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://securecode.dev/terms/</guid><description>&lt;p>These Terms govern use of the securecode.dev website.&lt;/p>
&lt;h2 id="website-use">Website use&lt;/h2>
&lt;p>The content on this site is provided for general informational purposes. It does not constitute legal advice, security certification, or a guarantee of any particular outcome.&lt;/p></description></item></channel></rss>