<?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>crowdstrike Archives | XOAP</title>
	<atom:link href="https://xoap.io/de/tag/crowdstrike/feed/" rel="self" type="application/rss+xml" />
	<link>https://xoap.io/de/tag/crowdstrike/</link>
	<description>Plattform für IT-Infrastruktur und Arbeitsplatzautomatisierung</description>
	<lastbuilddate>Wed, 04 Mar 2026 08:01:00 +0000</lastbuilddate>
	<language>de</language>
	<sy:updateperiod>
	stündlich	</sy:updateperiod>
	<sy:updatefrequency>
	1	</sy:updatefrequency>
	

<image>
	<url>https://xoap.io/wp-content/uploads/2023/11/cropped-favicon-32x32.png</url>
	<title>crowdstrike Archives | XOAP</title>
	<link>https://xoap.io/de/tag/crowdstrike/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Global outage takeaways: How to protect your organization</title>
		<link>https://xoap.io/de/global-outage-takeaways-how-to-protect-your-organization/</link>
		
		<dc:creator><![CDATA[Sinisa]]></dc:creator>
		<pubdate>Tue, 23 Jul 2024 12:02:08 +0000</pubdate>
				<category><![CDATA[Library]]></category>
		<category><![CDATA[crowdstrike]]></category>
		<category><![CDATA[global outage]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[xoap]]></category>
		<guid ispermalink="false">https://xoap.io/?p=14725</guid>

					<description><![CDATA[<p>XOAP's CTO offers key takeaways following the CrowdStrike incident, from an organizational and technical perspective.</p>
<p>The post <a href="https://xoap.io/de/global-outage-takeaways-how-to-protect-your-organization/">Global outage takeaways: How to protect your organization</a> appeared first on <a href="https://xoap.io/de">XOAP</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div data-elementor-type="wp-post" data-elementor-id="14725" class="elementor elementor-14725" data-elementor-post-type="post">
				<div class="elementor-element elementor-element-4f4a61c e-flex e-con-boxed e-con e-parent" data-id="4f4a61c" data-element_type="container" data-e-type="container" data-settings="{&quot;jet_parallax_layout_list&quot;:[]}">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-119f6a1 elementor-widget elementor-widget-text-editor" data-id="119f6a1" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p>We have all witnessed recent incidents that underscore the inherent fragility of IT systems.<br /><br />First, let me express my understanding of the trust placed in security agents deeply integrated within the OS to bolster system security. These agents, provided by reputable vendors, undergo rigorous testing to minimize potential issues, especially in high-impact scenarios.</p><p>However, despite our best efforts and the most stringent procedural tests, issues can still arise. After all, we are human, and errors are an inevitable part of our reality. I sympathize deeply with those affected by such incidents, recognizing the immense pressure and responsibility they bear.</p>								</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-0c1c0e8 e-flex e-con-boxed e-con e-parent" data-id="0c1c0e8" data-element_type="container" data-e-type="container" data-settings="{&quot;jet_parallax_layout_list&quot;:[]}">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-b71630c elementor-blockquote--skin-boxed elementor-widget elementor-widget-blockquote" data-id="b71630c" data-element_type="widget" data-e-type="widget" data-widget_type="blockquote.default">
				<div class="elementor-widget-container">
							<blockquote class="elementor-blockquote">
			<p class="elementor-blockquote__content">
				Incidents like this occur daily in various organizations, often on a smaller scale due to auto-updates.			</p>
					</blockquote>
						</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-19d424c e-flex e-con-boxed e-con e-parent" data-id="19d424c" data-element_type="container" data-e-type="container" data-settings="{&quot;jet_parallax_layout_list&quot;:[]}">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-3678952 elementor-widget elementor-widget-text-editor" data-id="3678952" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p>We must take a step back and consider how we can mitigate these issues in the future.</p><p>While it might be tempting to lay all the blame on <strong>CrowdStrike</strong>, it&#8217;s essential to remember that <b>both companies and end-users </b>share the responsibility for minimizing the impact of such incidents.</p><p>Here are several key points to consider.</p>								</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-ccc3c29 e-flex e-con-boxed e-con e-parent" data-id="ccc3c29" data-element_type="container" data-e-type="container" data-settings="{&quot;jet_parallax_layout_list&quot;:[]}">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-93bfcc8 elementor-widget elementor-widget-spacer" data-id="93bfcc8" data-element_type="widget" data-e-type="widget" data-widget_type="spacer.default">
				<div class="elementor-widget-container">
							<div class="elementor-spacer">
			<div class="elementor-spacer-inner"></div>
		</div>
						</div>
				</div>
				<div class="elementor-element elementor-element-2588d54 elementor-widget elementor-widget-heading" data-id="2588d54" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-default"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f5c3.png" alt="🗃" class="wp-smiley" style="height: 1em; max-height: 1em;" /> The organizational perspective</h2>				</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-7b639d0 e-flex e-con-boxed e-con e-parent" data-id="7b639d0" data-element_type="container" data-e-type="container" data-settings="{&quot;jet_parallax_layout_list&quot;:[]}">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-c707604 elementor-widget elementor-widget-text-editor" data-id="c707604" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p>First and foremost,<strong> establish robust testing stages</strong>. Implement processes to thoroughly test updates in automated environments before deploying them to production. When it comes to backup, <strong>implementing comprehensive backup strategies </strong>is critical in ensuring critical data and systems are backed up across multiple versions and locations.</p><p>In the event of total failure, you will need a clear, automated plan for redeploying your entire infrastructure.<strong> Develop redeployment plans </strong>and avoid the pitfall of treating server setup as a one-time task—automation is crucial. Moreover, pay attention to <strong>desktop readiness. </strong>Leverage available solutions to ensure desktops can be restored and operational within hours.</p><p>If you haven&#8217;t yet, <strong>adopt contemporary deployment methodologies and agile practices</strong>. Following incidents, conduct thorough <strong>postmortem analyses</strong> to identify and implement improvements.</p><p> </p>								</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-81f55ec e-flex e-con-boxed e-con e-parent" data-id="81f55ec" data-element_type="container" data-e-type="container" data-settings="{&quot;jet_parallax_layout_list&quot;:[]}">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-cb6ca42 elementor-widget elementor-widget-heading" data-id="cb6ca42" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-default"><img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f4bb.png" alt="💻" class="wp-smiley" style="height: 1em; max-height: 1em;" /> The technical perspective</h2>				</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-3565473 e-flex e-con-boxed e-con e-parent" data-id="3565473" data-element_type="container" data-e-type="container" data-settings="{&quot;jet_parallax_layout_list&quot;:[]}">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-8623afc elementor-widget elementor-widget-text-editor" data-id="8623afc" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><strong>Avoid &#8220;latest&#8221; and auto-updates on critical systems</strong>. While convenient, these can introduce unforeseen issues, so exercise caution.</p><p><strong>Testing should be done in controlled environments</strong>. Deploy nothing to production without thorough testing in a staging environment. <strong>Testing should also be done regularly</strong>. Conduct regular, comprehensive tests of your automation and deployment processes—not just annually.</p><p>To ensure rapid deployment in disaster scenarios, <strong>automate your infrastructure</strong> as much as possible and consider implementing <strong>automated testing</strong>. Testing processes enhanced with automation will catch issues early. For quicker recovery and reduced attack surfaces, transition critical infrastructure to <strong>containers and Kubernetes</strong>. Simultaneous failures can be mitigated by distributing infrastructure and critical components across <strong>multiple cloud providers and geographical locations</strong>.</p><p><strong>When it comes to standby snapshots, go cold</strong>. Maintain replicated, versioned snapshots of crucial backend systems and data as cold standby, since hot standby can replicate corrupted data.<br /><br />And last but not the least, <strong>rethink your security measures</strong>. Explore innovative security solutions that reduce dependency on full-blown desktops.</p><p> </p>								</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-798b3cd e-flex e-con-boxed e-con e-parent" data-id="798b3cd" data-element_type="container" data-e-type="container" data-settings="{&quot;jet_parallax_layout_list&quot;:[]}">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-4eb10cf elementor-widget elementor-widget-heading" data-id="4eb10cf" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-default">What do you think?</h2>				</div>
				</div>
				<div class="elementor-element elementor-element-33a3e14 elementor-widget elementor-widget-text-editor" data-id="33a3e14" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p>Before the end of this blog, I also want to highlight a particularly smart approach to addressing these issues, developed by <a href="https://www.linkedin.com/in/helgeklein/">Helge Klein</a> and the uberAgent team: <a href="https://uberagent.com/docs/uberagent/latest/troubleshooting/uberagent-driver-safety-net-feature/">UberAgent Driver Safety Net Feature</a>. Check it out!</p><p>If there&#8217;s anything I missed or if you have a different perspective, feel free to <a href="https://www.linkedin.com/posts/sinisasokolic_we-have-all-witnessed-recent-incidents-that-activity-7221440471867273217-FaZk?utm_source=share&amp;utm_medium=member_desktop" target="_blank" rel="noopener"><span style="text-decoration: underline;"><strong>share your thoughts here</strong></span></a>. <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f4ac.png" alt="💬" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>								</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-c3ece9f e-flex e-con-boxed e-con e-parent" data-id="c3ece9f" data-element_type="container" data-e-type="container" data-settings="{&quot;jet_parallax_layout_list&quot;:[]}">
					<div class="e-con-inner">
					</div>
				</div>
				</div><p>The post <a href="https://xoap.io/de/global-outage-takeaways-how-to-protect-your-organization/">Global outage takeaways: How to protect your organization</a> appeared first on <a href="https://xoap.io/de">XOAP</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>