<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Incident Response Archives - Secremedy</title>
	<atom:link href="https://secremedy.com/resources/category/incident-response/feed/" rel="self" type="application/rss+xml" />
	<link>https://secremedy.com/resources/category/incident-response/</link>
	<description>Proactive cybersecurity for UK SMEs</description>
	<lastBuildDate>Tue, 14 Jul 2026 15:19:15 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://secremedy.com/wp-content/uploads/2026/07/fav.svg</url>
	<title>Incident Response Archives - Secremedy</title>
	<link>https://secremedy.com/resources/category/incident-response/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Your site&#8217;s been hacked: here&#8217;s exactly what to do next</title>
		<link>https://secremedy.com/resources/website-hacked-what-to-do-next/</link>
					<comments>https://secremedy.com/resources/website-hacked-what-to-do-next/#respond</comments>
		
		<dc:creator><![CDATA[sajdoko]]></dc:creator>
		<pubDate>Mon, 15 Jun 2026 09:00:00 +0000</pubDate>
				<category><![CDATA[Incident Response]]></category>
		<category><![CDATA[Backups]]></category>
		<category><![CDATA[Ransomware]]></category>
		<guid isPermaLink="false">https://secremedy.com/website-hacked-what-to-do-next/</guid>

					<description><![CDATA[<p>The first hour matters most. A calm, step-by-step response plan for when the worst happens.</p>
<p>The post <a href="https://secremedy.com/resources/website-hacked-what-to-do-next/">Your site&#8217;s been hacked: here&#8217;s exactly what to do next</a> appeared first on <a href="https://secremedy.com">Secremedy</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A compromised website creates urgency, but the fastest route to recovery starts with containment and good evidence.</p>
<h2>Start with a clear baseline.</h2>
<p>Before buying another tool, document what you run and who has access. A short, accurate inventory makes security decisions easier.</p>
<h2>Focus on the gaps attackers can use.</h2>
<p>Incident response works best when ownership is clear and checks happen on schedule. Keep a record of what you find and assign every fix to a specific person.</p>
<ul>
<li>Confirm the systems and accounts in scope.</li>
<li>Remove access and software you no longer need.</li>
<li>Patch important weaknesses and verify the change.</li>
<li>Keep evidence your team can understand and reuse.</li>
</ul>
<blockquote>
<p>Simple controls applied consistently prevent more incidents than a long list of tools nobody owns.</p>
</blockquote>
<h2>Turn the findings into action.</h2>
<p>Set a review date and test the plan. If an area is difficult to verify internally, ask for an independent assessment.</p>
<p>The post <a href="https://secremedy.com/resources/website-hacked-what-to-do-next/">Your site&#8217;s been hacked: here&#8217;s exactly what to do next</a> appeared first on <a href="https://secremedy.com">Secremedy</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://secremedy.com/resources/website-hacked-what-to-do-next/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The SME ransomware readiness checklist</title>
		<link>https://secremedy.com/resources/sme-ransomware-readiness-checklist/</link>
					<comments>https://secremedy.com/resources/sme-ransomware-readiness-checklist/#respond</comments>
		
		<dc:creator><![CDATA[sajdoko]]></dc:creator>
		<pubDate>Wed, 20 May 2026 09:00:00 +0000</pubDate>
				<category><![CDATA[Incident Response]]></category>
		<category><![CDATA[Backups]]></category>
		<category><![CDATA[Ransomware]]></category>
		<guid isPermaLink="false">https://secremedy.com/sme-ransomware-readiness-checklist/</guid>

					<description><![CDATA[<p>Seven controls that make ransomware disruption shorter and easier to recover from.</p>
<p>The post <a href="https://secremedy.com/resources/sme-ransomware-readiness-checklist/">The SME ransomware readiness checklist</a> appeared first on <a href="https://secremedy.com">Secremedy</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Ransomware readiness means rehearsing your recovery before an attacker forces the test.</p>
<h2>Start with a clear baseline.</h2>
<p>Before buying another tool, document what you run and who has access. A short, accurate inventory makes security decisions easier.</p>
<h2>Focus on the gaps attackers can use.</h2>
<p>Ransomware preparation works best when ownership is clear and checks happen on schedule. Keep a record of what you find and assign every fix to a specific person.</p>
<ul>
<li>Confirm the systems and accounts in scope.</li>
<li>Remove access and software you no longer need.</li>
<li>Patch important weaknesses and verify the change.</li>
<li>Keep evidence your team can understand and reuse.</li>
</ul>
<blockquote>
<p>Simple controls applied consistently prevent more incidents than a long list of tools nobody owns.</p>
</blockquote>
<h2>Turn the findings into action.</h2>
<p>Set a review date and test the plan. If an area is difficult to verify internally, ask for an independent assessment.</p>
<p>The post <a href="https://secremedy.com/resources/sme-ransomware-readiness-checklist/">The SME ransomware readiness checklist</a> appeared first on <a href="https://secremedy.com">Secremedy</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://secremedy.com/resources/sme-ransomware-readiness-checklist/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
