<?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>A Personal CEO &#8211; РИСК-АКАДЕМИЯ &#8211; АНО ДПО ИСАР</title>
	<atom:link href="https://risk-academy.ru/tag/a-personal-ceo/feed/" rel="self" type="application/rss+xml" />
	<link>https://risk-academy.ru</link>
	<description>Управление рисками, риск менеджмент, обучение по управлению рисками, тренинг риск менеджмент</description>
	<lastBuildDate>Sat, 03 Oct 2020 08:14:48 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://raruswebsite.s3.amazonaws.com/wp-content/uploads/2018/02/10213225/cropped-favicon-32x32.png</url>
	<title>A Personal CEO &#8211; РИСК-АКАДЕМИЯ &#8211; АНО ДПО ИСАР</title>
	<link>https://risk-academy.ru</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Cybersecurity: A Personal CEO Liability</title>
		<link>https://risk-academy.ru/cybersecurity-a-personal-ceo-liability/</link>
		
		<dc:creator><![CDATA[riskacademy]]></dc:creator>
		<pubDate>Fri, 02 Oct 2020 18:49:16 +0000</pubDate>
				<category><![CDATA[Cyber Risks]]></category>
		<category><![CDATA[A Personal CEO]]></category>
		<category><![CDATA[ceo]]></category>
		<category><![CDATA[Cyberwarfare]]></category>
		<category><![CDATA[cyber-physical systems]]></category>
		<category><![CDATA[Analyst]]></category>
		<category><![CDATA[Data security]]></category>
		<category><![CDATA[CIO]]></category>
		<category><![CDATA[insurance policies]]></category>
		<category><![CDATA[Equifax]]></category>
		<category><![CDATA[Gregg Steinhafel]]></category>
		<guid isPermaLink="false">https://risk-academy.ru/cybersecurity-a-personal-ceo-liability/</guid>

					<description><![CDATA[“The analyst firm [Gartner] expects liability for cyber-physical systems (CPSs) incidents will pierce the corporate veil to personal liability for 75% of CEOs”. By 2024 the report predicts 75% of [&#8230;]]]></description>
										<content:encoded><![CDATA[<div>
<p>“The analyst firm [Gartner] expects liability for cyber-physical systems (CPSs) incidents will pierce the corporate veil to personal liability for 75% of CEOs”. By 2024 the report predicts 75% of CEOs will be personally liable for cybersecurity incidents. This means that insurance policies will no longer be able to cover the costs and damages related to a cyber incident. CEO personal liability will lead to significant financial and reputational repercussions in the event of a cyber incident.</p>
<h2><strong>Cybersecurity is Shifting to an Enterprise Issue</strong></h2>
<p>Previously, it was not the norm for CEOs to be directly responsible for cyberattacks. For example, when Equifax fell victim to one of these incidents, Moody’s downgraded their credit rating and their CIO was jailed for insider trading. Despite the fact that this attack affected 143 million consumers, no other executives were held liable. However, their CEO did resign due to the backlash the company received after the data breach. Target was a victim of a data breach in 2013 and their CEO at the time, Gregg Steinhafel resigned a few months following. In addition to reputational damage, CEOs may soon be personally liable for these&#8230;</p>
</div>
<p><a href="https://securityboulevard.com/2020/10/cybersecurity-a-personal-ceo-liability/">Read More&#8230;</a></p>
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<!-- RA -->
<ins class="adsbygoogle"
     style="display:inline-block;width:728px;height:90px"
     data-ad-client="ca-pub-6192158489792937"
     data-ad-slot="6411604661"></ins>
<script>
     (adsbygoogle = window.adsbygoogle || []).push({});
</script>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
