<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Legacy System Security on Ivaldo de Oliveira Batista Júnior</title><link>https://ivaldo.eti.br/tags/legacy-system-security/</link><description>Recent content in Legacy System Security on Ivaldo de Oliveira Batista Júnior</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Ivaldo de Oliveira Batista Júnior</copyright><lastBuildDate>Mon, 16 Nov 2026 19:00:00 -0300</lastBuildDate><atom:link href="https://ivaldo.eti.br/tags/legacy-system-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Software Hasn't Changed in a Year. Have Its Security Risks Stood Still Too?</title><link>https://ivaldo.eti.br/blog/dormant-software-security-risks/</link><pubDate>Mon, 16 Nov 2026 19:00:00 -0300</pubDate><guid>https://ivaldo.eti.br/blog/dormant-software-security-risks/</guid><description>&lt;p&gt;Every company has at least one system like this. It was built a few years ago, it works well, and nobody complains. The last code change happened more than a year ago. The team that built it has moved on to other projects — or left the company.&lt;/p&gt;
&lt;p&gt;The conclusion seems logical: &lt;strong&gt;if nothing changed, nothing got worse.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Unfortunately, that is not how security works.&lt;/p&gt;
&lt;p&gt;The code may be frozen. The world around it is not. New vulnerabilities are discovered every day in libraries, frameworks, operating systems, and components that system relies on. Software that was reasonably secure when it shipped can be exposed today — without a single line having changed.&lt;/p&gt;</description></item></channel></rss>