<?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"><channel><title><![CDATA[Topics tagged with awareness]]></title><description><![CDATA[A list of topics that have been tagged with awareness]]></description><link>https://board.circlewithadot.net/tags/awareness</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 02:19:42 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/tags/awareness.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Honeypot Experiment Shows the Relentless Reality of SSH Brute-Force Attacks]]></title><description><![CDATA[Honeypot Experiment Shows the Relentless Reality of SSH Brute-Force AttacksA 54-day SSH honeypot experiment recorded 269,000 automated connection attempts, revealing a trend of threat actors interested in Solana blockchain nodes and IoT devices using hardcoded credentials.**Disable password-based SSH authentication entirely and switch to SSH key authentication, as automated botnets are constantly hammering port 22 with millions of password guesses including default IoT and crypto-infrastructure credentials. Restrict SSH access to trusted IP addresses only (via firewall rules or VPN), change the default port if possible.**#cybersecurity #infosec #knowledge #awarenesshttps://beyondmachines.net/event_details/honeypot-experiment-shows-the-relentless-reality-of-ssh-brute-force-attacks-k-v-k-z-j/gD2P6Ple2L]]></description><link>https://board.circlewithadot.net/topic/1068493c-e75e-4926-9b80-71c0edd10ca3/honeypot-experiment-shows-the-relentless-reality-of-ssh-brute-force-attacks</link><guid isPermaLink="true">https://board.circlewithadot.net/topic/1068493c-e75e-4926-9b80-71c0edd10ca3/honeypot-experiment-shows-the-relentless-reality-of-ssh-brute-force-attacks</guid><dc:creator><![CDATA[beyondmachines1@infosec.exchange]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>