<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rodrigo Gutierrez on Medium]]></title>
        <description><![CDATA[Stories by Rodrigo Gutierrez on Medium]]></description>
        <link>https://medium.com/@ciberseguridad?source=rss-8c9ac025d9c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DT0SNZUdGtaXn7uwhITujw.jpeg</url>
            <title>Stories by Rodrigo Gutierrez on Medium</title>
            <link>https://medium.com/@ciberseguridad?source=rss-8c9ac025d9c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:28:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ciberseguridad/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[BrickStorm: when persistent access becomes infrastructure]]></title>
            <link>https://ciberseguridad.medium.com/brickstorm-when-persistent-access-becomes-infrastructure-78964db1ab9f?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/78964db1ab9f</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[brickstorm]]></category>
            <category><![CDATA[advancedthreats]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[ioc]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Wed, 17 Dec 2025 22:13:48 GMT</pubDate>
            <atom:updated>2025-12-17T22:15:15.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*nAC-Ce4rRW9y1T-CN9CwTw.png" /></figure><p>BrickStorm does not announce itself with spectacle. It does not rely on exotic zero-days, destructive payloads, or techniques designed to impress analysts. Its significance lies elsewhere, in a quieter and far more unsettling place: BrickStorm demonstrates that modern state-sponsored espionage has stopped behaving like an attack and started operating like infrastructure.</p><p>This campaign is not about breaking systems. It is about inhabiting them. BrickStorm embodies a strategic shift where intrusion is no longer an event but a condition, and persistence is not a tactic but an architectural goal. Every technical decision favors longevity, plausibility, and operational calm. The malware does not fight the environment; it blends into it, leveraging legitimate services, familiar protocols, and trusted platforms until it becomes indistinguishable from normal operations.</p><p>The danger is not technical novelty. The danger is normalization.</p><h3>From initial compromise to operational settlement</h3><p>One of the most persistent analytical mistakes when examining campaigns like BrickStorm is over-focusing on the initial access vector. In reality, initial compromise is almost incidental. BrickStorm appears after access has already been established, after credentials exist, and after the organization believes the worst moment has passed.</p><p>This is the phase of operational settlement. The attacker is no longer exploring or probing. The environment is known well enough to begin inhabiting it deliberately. BrickStorm is designed precisely for this stage. It arrives when defenses are relaxed, when patching has been completed, and when teams assume containment has been achieved.</p><p>Rather than expanding aggressively, the implant consolidates. It ensures it will survive reboots, updates, and operational noise. It observes, maps relationships, and waits. In many environments, this phase remains invisible because security programs are built to detect disruption, not presence.</p><h3>A backdoor designed to look ordinary</h3><p>Technically, BrickStorm is intentionally unremarkable. Its code favors stability and maintainability over heavy obfuscation or exotic execution chains. It functions as a persistent espionage backdoor, offering remote command execution, file management, and system reconnaissance, while maintaining a minimal footprint.</p><p>Communication with command-and-control infrastructure relies on common protocols and predictable timing. Traffic patterns resemble legitimate administrative or application behavior. There are no obvious spikes, no erratic beaconing, and no resource usage anomalies that would naturally draw attention.</p><p>This is not accidental. The malware is engineered to feel routine. In modern enterprise environments, routine is the safest hiding place.</p><p>BrickStorm illustrates a reality many defenders resist: advanced malware increasingly resembles enterprise software, not crimeware.</p><h3>Legitimacy as camouflage</h3><p>One of BrickStorm’s most effective characteristics is its deliberate reliance on legitimate infrastructure. Rather than deploying bespoke DNS services or suspicious hosting, the campaign uses widely trusted platforms and services to resolve names and maintain encrypted communication.</p><p>For defenders, this creates a structural dilemma. Blocking such traffic can disrupt business operations. Allowing it without scrutiny creates blind spots. BrickStorm thrives inside that tension.</p><p>This approach exposes a deeper flaw in many security architectures: the assumption that legitimacy implies safety. BrickStorm demonstrates that in modern espionage, legitimacy is often the most powerful camouflage available.</p><h3>Control planes as strategic footholds</h3><p>The campaign underscores the systemic risk of compromising platforms that operate as control planes rather than ordinary workloads. In virtualized environments, systems like vCenter are not just servers; they orchestrate identity, compute, storage, and access relationships across entire infrastructures.</p><p>BrickStorm leverages this centrality. After privilege escalation, the implant establishes persistence through system-level mechanisms, modifying initialization behavior to survive restarts and maintenance cycles. It places binaries in locations that closely mimic legitimate platform components, using naming conventions and directory structures that appear native.</p><p>This form of persistence does not rely on stealth through obscurity, but on credibility. The malware looks like it belongs.</p><p>Once embedded at this level, the attacker gains an observational vantage point that enables future operations against identity services, cryptographic material, and critical workloads, all without triggering traditional alarms.</p><h3>Windows as an extension of the settlement</h3><p>BrickStorm is not confined to appliances or Linux-based platforms. Variants targeting Windows environments demonstrate the same philosophy: persistence through native mechanisms, quiet execution, and integration into existing administrative workflows.</p><p>These variants rely on scheduled execution and plausible naming to maintain access, allowing the attacker to extend presence from infrastructure platforms into endpoints and servers. This expansion is strategic. Appliances provide durability and stealth; Windows systems provide access to credentials, email, internal documentation, and directory services.</p><p>Together, they form a complete espionage ecosystem. Addressing only one side leaves the other intact.</p><h3>Ivanti and the illusion of closure</h3><p>BrickStorm also highlights a dangerous operational illusion: the belief that patching ends the incident. In several observed scenarios, initial access was achieved through vulnerable remote access appliances. Patches were applied, vulnerabilities closed, and normal operations resumed.</p><p>What did not happen was eviction.</p><p>BrickStorm deploys precisely in this post-patch window, when organizations lower vigilance and assume resolution. The vulnerability is gone, but the attacker remains. Persistence mechanisms ensure continued access, while the absence of visible symptoms reinforces false confidence.</p><p>The lesson is uncomfortable but unavoidable: patching closes doors, but it does not check who entered before the door was closed.</p><h3>Lateral movement without disruption</h3><p>Unlike ransomware operations or financially motivated attacks, BrickStorm does not move laterally through brute force or noisy scanning. Movement is deliberate and informed. Valid credentials, existing trust relationships, and previously observed access patterns are used to transition between systems.</p><p>From an external perspective, this activity appears administrative. From an internal perspective, it blends seamlessly into operational workflows. Only contextual analysis can reveal inconsistencies, and only when signals are correlated over time.</p><p>This exposes another structural weakness. Many security operations centers are optimized for alert volume and speed, not for subtle behavioral analysis. BrickStorm produces uncertainty, not alarms, and uncertainty is often deprioritized.</p><h3>Intelligence, not disruption</h3><p>BrickStorm’s objective is not control or monetization. It is intelligence. Configuration data, architectural diagrams, internal communications, credential material, and decision-making artifacts form the core value of the operation.</p><p>This information does not generate immediate damage. Its impact emerges later, when negotiations fail unexpectedly, when strategic decisions appear anticipated, or when future operations unfold with unsettling precision.</p><p>Because the damage is delayed and indirect, it is often underestimated. BrickStorm exploits that blindness.</p><h3>Why traditional defenses fall short</h3><p>BrickStorm does not bypass security controls through clever evasion. It operates outside their conceptual assumptions. Firewalls, EDR platforms, and SIEM systems function as designed, but they are tuned for anomalies, signatures, and discrete events.</p><p>BrickStorm is consistent, contextual, and patient. It behaves normally, just not legitimately.</p><p>Effective detection requires deep environmental knowledge, dynamic baselining, and analysts capable of questioning what appears ordinary. It requires accepting that presence is the new threat model.</p><p>This level of maturity cannot be purchased as a product. It must be cultivated operationally.</p><h3>A strategic warning</h3><p>BrickStorm is not an outlier. It is a preview of how advanced espionage campaigns will increasingly operate: persistent, discreet, built on legitimate infrastructure, and focused on long-term strategic value.</p><p>The perimeter is no longer the primary battlefield. The real challenge lies in detecting adversaries who already behave like part of the system.</p><p>In modern espionage, success is not measured by how fast you enter, but by how long you remain unseen.</p><h3>Indicators of Compromise (IOCs), Operational Correlations, and Preventive Measures</h3><pre>&quot;Linux / Appliance / Virtualization Control Plane IOCs<br>Observed persistence and masquerading paths commonly associated with BrickStorm activity include system configuration and initialization directories typically reserved for legitimate platform components. The presence of new or modified binaries in these locations should be treated as high-confidence indicators of compromise, particularly when combined with outbound encrypted traffic patterns.&quot;</pre><pre>Notable paths and artifacts include:</pre><pre>/etc/sysconfig/ /etc/sysconfig/network/ /etc/sysconfig/init /opt/vmware/sbin/vmware-sphere /usr/java/jre-vmware/bin/updatemgr /home/vsphere-ui/ /home/bin/netmon /home/bin/logd /home/runtime/logd /home/config/logd.spec.cfg</pre><pre>The appearance of executable content or modified startup behavior in these locations strongly suggests post-exploitation persistence rather than legitimate platform updates.</pre><pre>Backdoor Functional Endpoints (Hunting Artifacts)<br>BrickStorm exposes a set of functional endpoints consistent with remote file management and command execution capabilities. These paths are not expected to be externally reachable or active in standard platform operation.</pre><pre>Examples include:</pre><pre>/api/file/change-dir /api/file/delete-dir /api/file/delete-file /api/file/mkdir /api/file/list-dir /api/file/rename /api/file/put-file /api/file/get-file /api/file/slice-up /api/file/file-md5</pre><pre>Detection of inbound or internal access to these endpoints warrants immediate investigation.</pre><pre>Network-Based Indicators and DoH Abuse<br>A defining characteristic of the campaign is the use of DNS over HTTPS (DoH) from systems that would not normally rely on public resolvers. DoH traffic originating from infrastructure management systems, virtualization platforms, or security appliances should be considered anomalous by default.</pre><pre>Commonly observed DoH endpoints include:</pre><pre>https://1.1.1.1/dns-query <a href="https://1.0.0.1/dns-query">https://1.0.0.1/dns-query</a> <a href="https://8.8.8.8/dns-query">https://8.8.8.8/dns-query</a> <a href="https://8.8.4.4/dns-query">https://8.8.4.4/dns-query</a> <a href="https://9.9.9.9/dns-query">https://9.9.9.9/dns-query</a> <a href="https://9.9.9.11/dns-query">https://9.9.9.11/dns-query</a> <a href="https://45.90.28.160/dns-query">https://45.90.28.160/dns-query</a> <a href="https://45.90.30.160/dns-query">https://45.90.30.160/dns-query</a> <a href="https://149.112.112.112/dns-query">https://149.112.112.112/dns-query</a></pre><pre>Persistent WebSocket Secure (WSS) sessions following DoH resolution from the same host significantly increase confidence of malicious activity.</pre><pre>Command-and-Control Domains and Infrastructure<br>The following domains and hosts have been associated with BrickStorm command-and-control or post-exploitation activity. Presence of outbound communication to these destinations, especially from non-endpoint infrastructure, should be treated as a confirmed compromise indicator.</pre><pre>opra1.oprawh.workers.dev ms-azure.azdatastore.workers.dev ms-azure.herokuapp.com oast.fun cpanel.netbar.org pan.xj.hk akapush.us.to</pre><pre>Observed IP addresses associated with related activity include:</pre><pre>8.218.240.85 98.142.138.21 103.13.28.40 103.27.110.83 103.73.66.37 193.149.129.191 206.188.196.199</pre><pre>Windows-Based IOCs<br>Windows variants of BrickStorm have been observed using plausible system-like filenames combined with scheduled execution for persistence.</pre><pre>Known filenames and hashes include:</pre><pre>CreatedUACExplorer.exe SHA-256: b42159d68ba58d7857c091b5acc59e30e50a854b15f7ce04b61ff6c11cdf0156</pre><pre>CreateUACExplorer.exe SHA-256: 42692bd13333623e9085d0c1326574a3391efcbf18158bb04972103c9ee4a3b8</pre><pre>Any scheduled task, service, or autorun mechanism invoking these binaries or similarly named executables should be treated as malicious.</pre><pre>High-Confidence Operational Correlations<br>The following correlations significantly increase detection confidence when observed together:</pre><pre>System initialization or configuration changes on virtualization or access appliances followed by outbound DoH traffic. Execution of binaries from platform system paths combined with long-lived encrypted sessions. Administrative-looking activity originating from infrastructure hosts shortly after VPN or appliance compromise. Post-patch environments exhibiting continued credential usage patterns inconsistent with normal administrative workflows.</pre><h3>Preventive Measures — Infrastructure and Network</h3><p>DNS over HTTPS should be treated as a managed service rather than generic HTTPS traffic. Infrastructure platforms should be restricted to internal resolvers, and outbound DoH traffic from control planes should be explicitly denied or heavily monitored.</p><p>Critical management systems must be isolated through strict segmentation and protected with multi-factor authentication. File integrity monitoring should be enforced on initialization paths and platform-specific system directories.</p><p>After any appliance-level vulnerability exposure, organizations should assume potential prior compromise and execute full credential rotation, integrity validation, and threat hunting rather than relying solely on patching.</p><h3>Preventive Measures — Endpoint and Identity</h3><p>Application control and execution monitoring should be enforced on Windows systems to detect plausibly named but unauthorized binaries. Scheduled task creation and modification should be treated as high-risk events when originating from unexpected contexts.</p><p>Identity systems require special attention following infrastructure compromise. Credential material, certificates, and directory services should be reviewed and rotated to prevent silent lateral movement and long-term persistence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78964db1ab9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The new era of third-party security: The perimeter you don’t control but that defines you]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://ciberseguridad.medium.com/the-new-era-of-third-party-security-the-perimeter-you-dont-control-but-that-defines-you-5f7e1751f640?source=rss-8c9ac025d9c8------2"><img src="https://cdn-images-1.medium.com/max/894/1*a-ojbvFi1DFHpCW_6THfVA.png" width="894"></a></p><p class="medium-feed-snippet">For nearly two decades, third-party security was treated as an administrative chore&#x200A;&#x2014;&#x200A;closer to bureaucracy than to cyber defense. Excel&#x2026;</p><p class="medium-feed-link"><a href="https://ciberseguridad.medium.com/the-new-era-of-third-party-security-the-perimeter-you-dont-control-but-that-defines-you-5f7e1751f640?source=rss-8c9ac025d9c8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://ciberseguridad.medium.com/the-new-era-of-third-party-security-the-perimeter-you-dont-control-but-that-defines-you-5f7e1751f640?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f7e1751f640</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[risk]]></category>
            <category><![CDATA[third-party]]></category>
            <category><![CDATA[grc]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Tue, 02 Dec 2025 14:43:19 GMT</pubDate>
            <atom:updated>2025-12-02T14:43:19.521Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Phantom Risk: How AI in the Financial Sector Is Exposing Its Internal Logic Through Unintended…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://ciberseguridad.medium.com/the-phantom-risk-how-ai-in-the-financial-sector-is-exposing-its-internal-logic-through-unintended-c6dd79d85400?source=rss-8c9ac025d9c8------2"><img src="https://cdn-images-1.medium.com/max/954/1*ZY7WZa1yPJ_clmZjsC08HA.png" width="954"></a></p><p class="medium-feed-snippet">The emergence of form leakage in a sector built on patterns</p><p class="medium-feed-link"><a href="https://ciberseguridad.medium.com/the-phantom-risk-how-ai-in-the-financial-sector-is-exposing-its-internal-logic-through-unintended-c6dd79d85400?source=rss-8c9ac025d9c8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://ciberseguridad.medium.com/the-phantom-risk-how-ai-in-the-financial-sector-is-exposing-its-internal-logic-through-unintended-c6dd79d85400?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6dd79d85400</guid>
            <category><![CDATA[risk]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[financial]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Wed, 19 Nov 2025 04:43:05 GMT</pubDate>
            <atom:updated>2025-11-19T04:43:05.035Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Intelligent Visitor: Real Strategies for Exploring the Darkweb Without Leaving Traces]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://ciberseguridad.medium.com/the-intelligent-visitor-real-strategies-for-exploring-the-darkweb-without-leaving-traces-2a24b29b3497?source=rss-8c9ac025d9c8------2"><img src="https://cdn-images-1.medium.com/max/989/1*UfILHH-_Lkl20uW7HXbS0w.png" width="989"></a></p><p class="medium-feed-snippet">A Territory That Watches You Before You See Anything</p><p class="medium-feed-link"><a href="https://ciberseguridad.medium.com/the-intelligent-visitor-real-strategies-for-exploring-the-darkweb-without-leaving-traces-2a24b29b3497?source=rss-8c9ac025d9c8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://ciberseguridad.medium.com/the-intelligent-visitor-real-strategies-for-exploring-the-darkweb-without-leaving-traces-2a24b29b3497?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a24b29b3497</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Thu, 13 Nov 2025 03:18:26 GMT</pubDate>
            <atom:updated>2025-11-13T03:18:26.585Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[At the core of Microsoft Windows Server’s ecosystem lies a principle so ingrained it’s rarely…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://ciberseguridad.medium.com/at-the-core-of-microsoft-windows-servers-ecosystem-lies-a-principle-so-ingrained-it-s-rarely-cd19167c3def?source=rss-8c9ac025d9c8------2"><img src="https://cdn-images-1.medium.com/max/989/1*tjEwy1jGPYkk-iRGurWBjw.png" width="989"></a></p><p class="medium-feed-snippet">That same mechanism, however, became a systemic liability. The vulnerability CVE-2025&#x2013;59287 exposed a critical flaw in WSUS: an insecure&#x2026;</p><p class="medium-feed-link"><a href="https://ciberseguridad.medium.com/at-the-core-of-microsoft-windows-servers-ecosystem-lies-a-principle-so-ingrained-it-s-rarely-cd19167c3def?source=rss-8c9ac025d9c8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://ciberseguridad.medium.com/at-the-core-of-microsoft-windows-servers-ecosystem-lies-a-principle-so-ingrained-it-s-rarely-cd19167c3def?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd19167c3def</guid>
            <category><![CDATA[updates]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[microsoft]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Wed, 12 Nov 2025 18:59:48 GMT</pubDate>
            <atom:updated>2025-11-12T18:59:48.123Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Free, but Not Innocent: Anatomy of the Legal Fraud Dominating Online Commerce]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://ciberseguridad.medium.com/free-but-not-innocent-anatomy-of-the-legal-fraud-dominating-online-commerce-6ba6eb9bc183?source=rss-8c9ac025d9c8------2"><img src="https://cdn-images-1.medium.com/max/786/1*eVKI7jTv8ZAUci0jTP0duw.png" width="786"></a></p><p class="medium-feed-snippet">The Mirage of &#x201C;Free&#x201D;</p><p class="medium-feed-link"><a href="https://ciberseguridad.medium.com/free-but-not-innocent-anatomy-of-the-legal-fraud-dominating-online-commerce-6ba6eb9bc183?source=rss-8c9ac025d9c8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://ciberseguridad.medium.com/free-but-not-innocent-anatomy-of-the-legal-fraud-dominating-online-commerce-6ba6eb9bc183?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ba6eb9bc183</guid>
            <category><![CDATA[commerce]]></category>
            <category><![CDATA[legal]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[online-business]]></category>
            <category><![CDATA[fraud]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 01:06:47 GMT</pubDate>
            <atom:updated>2025-11-11T01:06:47.212Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[After the Fire: the Human and Technical Anatomy of Cyber Recovery]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://ciberseguridad.medium.com/after-the-fire-the-human-and-technical-anatomy-of-cyber-recovery-35edd559a58f?source=rss-8c9ac025d9c8------2"><img src="https://cdn-images-1.medium.com/max/865/1*dCxIhCoQR9mjNKfv-0LKSQ.png" width="865"></a></p><p class="medium-feed-snippet">Read for Free:</p><p class="medium-feed-link"><a href="https://ciberseguridad.medium.com/after-the-fire-the-human-and-technical-anatomy-of-cyber-recovery-35edd559a58f?source=rss-8c9ac025d9c8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://ciberseguridad.medium.com/after-the-fire-the-human-and-technical-anatomy-of-cyber-recovery-35edd559a58f?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/35edd559a58f</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[resilience]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Mon, 27 Oct 2025 11:12:17 GMT</pubDate>
            <atom:updated>2025-10-27T11:12:17.117Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Inside the Mind of an Antivirus]]></title>
            <link>https://ciberseguridad.medium.com/inside-the-mind-of-an-antivirus-e49ba3d910ef?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e49ba3d910ef</guid>
            <category><![CDATA[antivirus]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[edr]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Fri, 24 Oct 2025 01:47:59 GMT</pubDate>
            <atom:updated>2025-10-24T01:47:59.256Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*zRkWiL-IUAeEdevMmNPJHw.png" /></figure><p>A modern antivirus doesn’t “see” files; it interprets <strong>behavior</strong>. What looks to us like a program scanning folders is, in truth, a silent observer reconstructing every movement within the operating system. Imagine a digital psychologist watching how programs behave, how they “think,” and how they interact. This psychologist doesn’t judge by appearance — a harmless-looking icon may conceal something entirely different — but by how a program moves and what relationships it forms.</p><p>In its eyes, every system action carries meaning. Opening a port (a communication channel between the computer and the outside world) may be legitimate — or an attempt to leak data. Editing the Windows Registry may be maintenance — or sabotage. The distinction lies not in the action itself, but in <strong>context</strong>: <em>when</em>, <em>where</em>, and <em>why</em> it happens.</p><p>Antiviruses no longer focus on finding “viruses” in the traditional sense — those self-replicating bits of code from the past. Today, they watch the system as if it were a living organism. They collect telemetry (data about the system’s own behavior), build models of normality, and flag deviations that may signal infection or manipulation. In other words, they define <em>maliciousness</em> not by what something looks like, but by how far it strays from the ordinary.</p><p>When a process injects itself into another (embedding code into a running program), when it creates invisible threads, or when it elevates privileges beyond its scope, the detection engine reacts. Not because it <em>knows</em> who the attacker is, but because it recognizes that <strong>no innocent entity acts this way</strong>. The antivirus, then, is less a police officer chasing criminals and more a therapist detecting patterns of deviant behavior. It doesn’t hunt the crime; it senses the intention. Every alert is an algorithmic judgment — a silent verdict on what the system deems “healthy” or “sick.”</p><h4>The Language of Misbehavior</h4><p>Maliciousness is not a moral term — it’s a pattern. Antivirus and EDR systems (Endpoint Detection and Response, monitoring each device individually) translate the chaos of software into a language they can understand. In that language, every instruction, every system call, every attempt to write or read from memory carries meaning. Opening a connection to an unknown address might mean “saying hello”… or “sending secrets.” The difference lies in perceived intention.</p><p>Modern detection engines no longer isolate single events. They analyze <strong>sequences</strong>. If a process downloads a file, decompresses it, executes code directly in memory, and then deletes itself, the suspicious part isn’t any one action but <strong>the story</strong> they tell together. The antivirus doesn’t read words — it reads sentences; it doesn’t watch gestures — it studies behavior. This approach, known as <em>heuristic</em> or <em>behavioral detection</em>, is the core of modern defense, enabling systems to recognize new threats even before they are formally classified.</p><p>The challenge arises when legitimate creativity looks too much like malicious ingenuity. A system administrator running automation scripts may trigger the same alerts as an attacker: memory manipulation, remote access, bulk modification of files. That’s why security engines don’t just observe — they infer <em>why</em>. They analyze file origin, digital signatures, behavioral history, and network reputation. Each decision is probabilistic rather than absolute.</p><p>An antivirus, like any good psychologist, interprets signs. It doubts, suspects, sometimes errs. But its purpose is to identify intentions disguised as routine. It doesn’t judge lines of code — it judges <strong>patterns of conduct</strong>. In a sense, modern antivirus software mirrors our own human perception: it judges not by what it sees, but by what it understands.</p><h4>From Suspicious File to Hostile Process</h4><p>For years, antivirus software functioned like a museum of threats. Each known virus left its signature, and the software’s job was to compare every new file against that immense gallery of fingerprints. It was a reactive model — useful, but doomed. Attackers soon learned to mutate their creations. Changing just a few bytes made a virus look new while acting exactly the same.</p><p>That realization forced a transformation: security had to stop “memorizing enemies” and start <strong>recognizing behavior</strong>. Today, when an antivirus or EDR inspects a system, it doesn’t look for familiar names or extensions — it observes what each process <em>does while alive</em>. If a program injects code into explorer.exe, opens anonymous pipes (hidden communication channels between processes), modifies the master boot record (MBR), or schedules hidden tasks for reboot persistence, the system raises an alert.</p><p>In Linux, the story is similar: it watches for ptrace (a function used to spy on other processes), executions inside /tmp (a temporary folder never meant for binaries), or privilege escalation through sudo. On macOS, eyes focus on framework alterations, sandbox violations, and unauthorized keychain access.</p><p>In every environment, the same principle reigns: <strong>contextual anomaly</strong>. What matters isn’t the act itself but whether it fits the expected pattern. The antivirus stopped being a border guard checking passports and became a physician reading symptoms. And like any diagnosis, it’s imperfect — but it learns. Every second, millions of devices feed anonymized telemetry into vast clouds, where collective behavior shapes what the system will consider “malicious” tomorrow. Every protected device participates, unknowingly, in teaching machines what evil looks like in code.</p><h4>EDR: When Behavior Outweighs the File</h4><p>EDR systems represent the maturity of that evolution. They don’t just observe — they <strong>reconstruct stories</strong>. While traditional antivirus engines monitor isolated actions, EDR platforms weave them into coherent narratives. They log what process launched what, when, with which permissions, and what it touched afterward. Then they connect those dots like a forensic analyst building a timeline of events.</p><p>Correlation is the heart of EDR — the art of linking signals that, in isolation, mean nothing. A download may be harmless. An execution may be routine. But if both occur in sequence, followed by a change to a system service, the meaning shifts: from administration to intrusion. EDR is cybersecurity’s detective instinct made algorithm.</p><p>It also introduces something revolutionary: <strong>retrospection</strong>. An EDR can revisit the past. If an action once deemed safe is later found to be part of an attack, the system rewinds history and updates its judgment. It’s as though the antivirus had learned to <em>regret</em>.</p><p>Strategically, this changes everything. Security stops being a static shield and becomes a living narrative. Machines no longer just block — they <strong>tell stories</strong> about what was attempted against them. And within those stories lie clues about attacker psychology, methods, and failure. EDR, at its essence, is the silent chronicler of the invisible conflict between systems and humans.</p><h4>The Dilemma of the False Positive</h4><p>If the antivirus is a judge, its worst mistake is condemning the innocent. False positives — the mislabeling of benign activity as malicious — are the mirror image of paranoia. In a corporation, a false positive can cost more than an actual virus: halting production lines, freezing servers, or disabling financial systems.</p><p>Developers of security tools know this. They refine algorithms relentlessly, test millions of samples, adjust suspicion thresholds, and train artificial intelligence to distinguish <em>unusual</em> from <em>dangerous</em>. But perfection remains impossible. Every environment has its own definition of normal. A biotech lab, a bank, and a film studio all exhibit radically different digital behaviors.</p><p>Attackers exploit that ambiguity. They operate in the gray zones between normal and suspicious. Some craft <em>gray malware</em> — software that performs harmful acts disguised as maintenance. Others weaponize legitimate system tools like cmd.exe or PowerShell, turning them into instruments of stealth. This technique, called <em>living off the land</em>, allows attackers to blend perfectly into the environment they’re exploiting.</p><p>That’s why the best systems learn to <strong>coexist with doubt</strong>. They no longer act impulsively. They observe, confirm, and then respond. The antivirus of tomorrow will not be the fastest to trigger — but the most precise in interpretation. The future belongs to empathy in code: algorithms that understand when a suspicious pattern is merely a misunderstood human reflex.</p><h4>The Future of Digital Judgment</h4><p>We are entering an era in which antivirus engines will cease to be tools and become <strong>interpreters of human behavior encoded in software</strong>. New systems powered by artificial intelligence learn from millions of examples — both malicious and legitimate — developing a kind of statistical intuition. They don’t just analyze commands; they recognize context.</p><p>Soon, protection platforms will understand <em>why</em> someone performs an action, not just <em>what</em> the action is. If an administrator logs in at midnight, the system will judge not by the clock but by coincidence: Is there an encrypted tunnel to an unusual country? Is a script erasing logs in parallel? Detection will become narrative — it will interpret <strong>intention</strong> before evidence.</p><p>But this sophistication raises deeper questions. Do we really want a machine to interpret our motives? What does “malicious” mean when the verdict is delivered by a statistical model? As antivirus and EDR systems grow more intelligent, they become moral arbiters of digital behavior. Between protection and surveillance lies a vanishing line.</p><p>The mind of the antivirus, in the end, mirrors our own. It reveals that the line between curiosity and manipulation, maintenance and sabotage, security and control, is always a matter of context. And on that frontier, cybersecurity ceases to be purely technical — it becomes philosophical. To understand maliciousness is, ultimately, to understand ourselves.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e49ba3d910ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Invisible Architecture: Cyberdefense in the Quantum Internet Era]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://ciberseguridad.medium.com/the-invisible-architecture-cyberdefense-in-the-quantum-internet-era-bac3e4c611a0?source=rss-8c9ac025d9c8------2"><img src="https://cdn-images-1.medium.com/max/782/1*8ZrCHW8D_lHIsNbKR2cY4A.png" width="782"></a></p><p class="medium-feed-snippet">The dawn of the entangled network</p><p class="medium-feed-link"><a href="https://ciberseguridad.medium.com/the-invisible-architecture-cyberdefense-in-the-quantum-internet-era-bac3e4c611a0?source=rss-8c9ac025d9c8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://ciberseguridad.medium.com/the-invisible-architecture-cyberdefense-in-the-quantum-internet-era-bac3e4c611a0?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/bac3e4c611a0</guid>
            <category><![CDATA[digital-trust]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[quantum]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[quantum-internet]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 02:20:16 GMT</pubDate>
            <atom:updated>2025-10-15T02:20:16.658Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ISO 27701:2025 — The New Era of Certifiable Privacy]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://ciberseguridad.medium.com/iso-27701-2025-the-new-era-of-certifiable-privacy-bd234da55120?source=rss-8c9ac025d9c8------2"><img src="https://cdn-images-1.medium.com/max/782/1*bffXCi0uBtqVMl9l9Zfo2g.png" width="782"></a></p><p class="medium-feed-snippet">For decades, information security dictated the rules of the game. Everything revolved around confidentiality, integrity, and availability&#x2026;</p><p class="medium-feed-link"><a href="https://ciberseguridad.medium.com/iso-27701-2025-the-new-era-of-certifiable-privacy-bd234da55120?source=rss-8c9ac025d9c8------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://ciberseguridad.medium.com/iso-27701-2025-the-new-era-of-certifiable-privacy-bd234da55120?source=rss-8c9ac025d9c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd234da55120</guid>
            <category><![CDATA[digital-governance]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[iso27701]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Rodrigo Gutierrez]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 01:59:23 GMT</pubDate>
            <atom:updated>2025-10-15T01:59:23.501Z</atom:updated>
        </item>
    </channel>
</rss>