European Cybersecurity Implementation Overview Res Eng 0814
European Cybersecurity Implementation Overview Res Eng 0814
European Cybersecurity Implementation Overview Res Eng 0814
Implementation: Overview
www.isaca.org/cyber
About ISACA
With more than 115,000 constituents in 180 countries, ISACA (www.isaca.org) helps business
and IT leaders build trust in, and value from, information and information systems. Established
in 1969, ISACA is the trusted source of knowledge, standards, networking, and career
development for information systems audit, assurance, security, risk, privacy and governance
Provide feedback:
www.isaca.org/EU-cyber-implementation
cybersecurity professionals, and COBIT, a business framework that helps enterprises govern
professionals. ISACA offers the Cybersecurity Nexus, a comprehensive set of resources for
and manage their information and technology. ISACA also advances and validates business-
critical skills and knowledge through the globally respected Certified Information Systems
Auditor (CISA), Certified Information Security Manager (CISM ), Certified in the Governance
of Enterprise IT (CGEIT) and Certified in Risk and Information Systems Control (CRISC)
Disclaimer
ISACA has designed and created European Cybersecurity Implementation: Overview white paper (the Work) primarily
as an educational resource for assurance, governance, risk and security professionals. ISACA makes no claim that use of
any of the Work will assure a successful outcome. The Work should not be considered inclusive of all proper information,
procedures and tests or exclusive of other information, procedures and tests that are reasonably directed to obtaining
the same results. In determining the propriety of any specific information, procedure or test, assurance, governance, risk
and security professionals should apply their own professional judgement to the specific circumstances presented by the
particular systems or information technology environment.
ACKNOWLEDGEMENTS
Development Team
Rolf M. von Roessing
Ivo Ivanovs
Samuel Linares
Charlie McMurdie
PricewaterhouseCoopers, UK
Andreas Teuscher
CISA, CGEIT, CRISC,
Sick AG, Germany
Expert Reviewers
Jesper Hansen
Martins Kalkis
CISM,
Latvian Mobile Telephone, Latvia
Aare Reintam
CISA,
Estonian Information System Authority, Estonia
Andrea Rigoni
Intellium Ltd., UK
Ramses Gallego
Theresa Grafenstine
Vittal R. Raj
Tony Hayes
Gregory T. Grocholski
CISA,
The Dow Chemical Co., USA, Past International President
Debbie A. Lew
CISA, CRISC,
Ernst & Young LLP, USA, Director
Knowledge Board
Steven A. Babb
Manuel Aceves
Sanjay Bahl
CISM, CIPP,
India
Brent Conran
Derek Grocke
HAMBS, Australia
Samuel Linares
Marc Sachs
Verizon, USA
Charlie Blanchard
Steven A. Babb
Phil J. Lageschulte
Garry J. Barnes
Anthony P. Noble
Sushil Chatterji
Rosemary M. Amato
Robert E Stroud
CGEIT, CRISC,
CA, USA, International President
Jamie Pasfield
CGEIT,
Edutech Enterprises, Singapore
CGEIT, CPA,
KPMG LLP, USA
CISA,
Viacom, USA
Robert A. Clyde
CISM,
Adaptive Computing, USA, Vice President
Ub
ss
ne
i
s
Bu ety
c
i
i
r
nt Soc
e
c
d
IT- an
iqu
it
(Al ous B
wa ro
ys adb
On an
)
d
Social Stratification
of In-depth IT Skills
FIGURE
FIGURE
Creating a Culture
of Security
European Cybersecurity
Implementation Series
Advanced Persistent
Threats: How to Manage
the Risk to Your Business
European Cybersecurity
Implementation: Overview
Transforming Cybersecurity
Responding to Targeted
Cyberattacks
European Cybersecurity
Implementation:
Risk Guidance
European Cybersecurity
Implementation: Resilience
European Cybersecurity
Implementation: Assurance
European Cybersecurity
Implementation: Audit
Programme
1
2
The European Union (EU) includes the 28 member states, e.g., France, The Netherlands and Spain, and any of their territories outside of Europe.
Associated countries are linked to the EU by treaties or other agreements. Therefore, part of their cybersecurity policy and strategy may be aligned with EU guidance.
Examples of associated countries include the British Channel Islands, Liechtenstein and Switzerland.
PURPOSE
The European Cybersecurity Implementation Series is
designed primarily to provide practical implementation
guidance that is aligned with European requirements and
good practice.
TARGET AUDIENCES
The European Cybersecurity Implementation Series is
organised to provide targeted insights to the various
FIGURE
European
Cybersecurity
Implementation
Series Papers
Target Audience
CxO/Senior
Management
(Business)
Chief Information
Officer (CIO)/IT
Management
Information/
Cybersecurity
Practitioner
Auditor/
Reviewer
Overview
Risk Guidance
Resilience
Assurance
Audit Programme
The European cybersecurity laws and regulations are usually more stringent for industry sectors that are regulated
or classified as critical infrastructure than for unregulated industries. However, the presence of legal provisions or
regulations is not the only cybersecurity driver. Some industry sectors have experienced a higher rate of cybercrime,
cyberwarfare or industrial espionage than others.
Figure 4 shows some of the industry sectors that can benefit particularly from specific papers in the
European Cybersecurity Implementation Series. This list is by no means exhaustive, but provides
suggestions for recommended reading.
FIGURE
Industry Sector
Overview
Risk Guidance/
Resilience/
Assurance3
Audit
Programme4
Public
Telecommunications
Finance and Insurance
Health care
Critical
Infrastructures
Automotive
IT service providers
Audit
Consulting
Use this guidance in collaboration with national institutions and their individual guidance on cybersecurity.
The Audit Programme paper is for practitioners or specialists tasked with performing reviews or audits.
Financial institutions and insurers should also refer to their specific industry sector regulation, e.g., Basel III.
6
IT service providers should review their client base for any inherited regulatory requirements. For the risk, resilience and assurance
requirements and potential audits, these providers should also refer to ISAE 3402 and national implementations. respectively.
3
4
5
Enterprises should distinguish between standard (lower-level) information security and cybersecurity; the difference is in
the scope, motive, opportunity and method of the attack (see figure 5). Cybersecurity should focus on APTs to enable a
clear and targeted set of cybersecurity measures and actions. This is shown in figure 5.
FIGURE
Cyberattack Taxonomy13
Unsophisticated Attackers
(Script Kiddies)
Corporate Espionage
(insiders)
Sophisticated Attackers
(Hackers)
State-sponsored Attacks
Advanced Persistent Threat (APT)
You are targeted because of who you are,
what you do, or the value of your IP.
Personal Gain
Intelligence
Gathering
Hackers
Script Kiddies
Risk
Insiders
APT
State-sponsored
Espionage and
Weaponization
Data
Exfiltration
Money
APT
Life Cycle
Privilege
Escalation
Amusement/
Experimentation/
Nuisance
Initial
Exploitation
Command
and Control
Attacker Resources/Sophistication
1980s/1990s
BrainBoot/Morris Worm
Polymorphic Viruses
Michelangelo
Anna Kournikova
Sircam
Code Red and Nimda
SQL Slammer
Blaster
Sobig
MyDoom
Netsky
Sasser
Storm botnet
Koobface
Conflicker
Aurora
Mariposa
Stuxnet
WikiLeaks
Anonymous
LulzSec
2012
SpyEye/Zeus
Duqu
Flame
FIGURE
Economic
14
Low to Medium
Level Attacks
(Infosec)
APT Attacks
(Cybersec)
Technical
13
Social
FIGURE
HIGH
Cyberwarfare
EFFORT/SOPHISTICATION
Directed APT
LOW
Spear phishing
Zero-day/
complex
exploits
Simple
malware attacks
LOW
Cybersecurity
scope
15
GUARDED
Information
security scope
ELEVATED
HIGH
SEVERE
10
16
Enterprises should no
longer consider themselves
uninteresting, because new
automated attack methods
will perform global and
indiscriminate dragnet
sweeps for weaknesses and
vulnerabilities.
17
11
Information security
ERM
Organisational resilience
Information assurance
See information security, cybercrime and cybersecurity surveys that are published by international consulting firms and vendors, such as the following:
Special Eurobarometer 390 Cyber Security Report, July 2012, at http://ec.europa.eu/public_opinion/archives/ebs/ebs_390_en.pdf
Special Eurobarometer 404 Cyber Security Report, November 2013, at http://ec.europa.eu/public_opinion/archives/ebs/ebs_404_en.pdf
2013 Information Security Breaches Survey Technical Report, Department for Business Innovation & Skills, at www.gov.uk/government/uploads/system/uploads/attachment_data/file/200455/
bis-13-p184-2013-information-security-breaches-survey-technical-report.pdf
Symantec, 2013 Cost of Data Breach Study: Global Analysis, May 2013, conducted by Ponemon Institute LLC, www4.symantec.com/mktginfo/whitepaper/053013_GL_NA_WP_Ponemon2013-Cost-of-a-Data-Breach-Report_daiNA_cta72382.pdf
CERT Division of the Software Engineering Institute (SEI) studies at www.cert.org/cybersecurity-engineering/publications/index.cfm
19
Examples include ISACA and other industry associations.
20
For example, see the LKEX exercise in Germany, which was the scenario of a widespread cyberattack on selected critical infrastructures, www.bbk.bund.de/SharedDocs/Pressemitteilungen/BBK/
DE/2011/PM_Luekex_2011_IT_Sicherheit_auf_Pruefstand.html (in German).
18
12
21
FIGURE
Goals Cascade21
Stakeholders Drivers
(Environment, Technology Evolution, ...)
Influence
Stakeholders Needs
Benefits
Realisation
Risk
Optimisation
Resource
Optimisation
Cascade to
Enterprise Goals
Cascade to
IT-related Goals
Cascade to
Enablers Goals
Source: COBIT 5, ISACA, USA, 2012, figure 4
The goals cascade is from COBIT 5, an internationally recognised framework for governance, risk management and compliance (GRC) in IT and related technologies.
It is freely available at www.isaca.org/cobit.
13
23
EUROPOL24
United Nations cybercrime statistics25
National statistics offices or agencies
Incidental information drawn from various sources26
Industry surveys conducted by commercial firms27
Most of the extant information emphasises the fact that
cyberattacks are becoming more frequent and tend to have
a more significant and protracted impact on enterprises.
Further empirical data are often available in incidental
newspaper articles that report on individual cyberattacks or
cybersecurity failures.
In practice, the business case requires data about the
business impact of successful (or attempted) cyberattacks.
Enterprises can leverage many publicly available sources
to provide a well-founded picture, sometimes by sector or
size, including the following:
n example standard is ISO 27032, which provides informal guidance on cybersecurity. Likewise, the lead standards ISO 27001 and ISO 22301 provide specifications on information security
A
management systems and business continuity management systems, respectively.
23
For examples, see Special Eurobarometer 390 Cyber Security Report, July 2012, at http://ec.europa.eu/public_opinion/archives/ebs/ebs_390_en.pdf, and Special Eurobarometer 404 Cyber Security
Report, November 2013, at http://ec.europa.eu/public_opinion/archives/ebs/ebs_404_en.pdf.
24
For information about the EUROPOL European Cybercrime Centre, see https://www.europol.europa.eu/ec3.
25
For an example, see UNDOC Comprehensive Study on Cybercrime, February 2013, at www.unodc.org/documents/organized-crime/UNODC_CCPCJ_EG.4_2013/CYBERCRIME_STUDY_210213.pdf.
26
For an example, see Cyber Crime Originates in Europe: Statistics and Trend Report, 4 August 2013, at http://www.pymnts.com/uncategorized/2013/cyber-crime-originates-in-europe-statistics-and-
trends-report/.
27
Some of these surveys are commissioned by government agencies. For an example, see 2013 Information Security Breaches Survey Technical Report, Department for Business Innovation & Skills,
at www.gov.uk/government/uploads/system/uploads/attachment_data/file/200455/bis-13-p184-2013-information-security-breaches-survey-technical-report.pdf.
28
Symantec, 2013 Cost of Data Breach Study: Global Analysis, May 2013, conducted by Ponemon Institute LLC, at www4.symantec.com/mktginfo/whitepaper/053013_GL_NA_WP_Ponemon-2013Cost-of-a-Data-Breach-Report_daiNA_cta72382.pdf.
29
For an example, see 2013 Information Security Breaches Survey Executive Summary, Department for Business Innovation & Skills, at www.pwc.co.uk/assets/pdf/cyber-security-2013-exec-summary.
pdf.
30
Many CERT studies are available at www.cert.org/cybersecurity-engineering/publications/index.cfm.
22
14
COST-BENEFIT CONSIDERATIONS
The cost of cybersecurity can appear high when
compared to standard information security. For many
years, budgetsboth capital expenditure and operational
expenditurehave been under pressure. The cost of
information security is featured almost always in surveys
as a limiting factor to achieving innovation or higher levels
of protection.
Much of this has changed in line with the current risk and
threat landscape. The business case now addresses a
changed scenario, in which targeted attacks are directed
against the enterprise by well-organised individuals
or groups. Therefore, security is no longer a cost item
with an uncertain return. It is a necessary precaution
to prevent or mitigate clearly foreseeable events.
Enterprises should regard cyberattacks as a certainty
rather than a probability.
When formulating the business case for cybersecurity,
enterprises should include all dimensions of cost
(particularly the cost of shortcomings or accepting too
much risk) and benefits, such as preserving corporate
reputation and integrity, including the following:
31
32
As examples, consider the Zurich Insurance Group (2011) and Swisscom (2013) incidents, which both relate to lost or stolen backup tapes containing sensitive data.
As an example, consider the Snapchat vulnerability (2013), which was discovered on iPhones, and the subsequent drop in market value that Snapchat experienced.
15
The COBIT 5 framework offers useful insights on substantiating and demonstrating business value as part of good
governance and management, and enterprises can use the goals cascade to demonstrate the benefits of cybersecurity.
Other frameworks33 and standards provide additional guidance on how to demonstrate the business value of
cybersecurity. When presenting the business case, experts and cybersecurity practitioners should ensure that they
address all aspects of the GRC triad and the goals cascade and possibly include the consequences for having the
balanced scorecard (BSC) and other measurement instruments in place.
It should further be noted that cybersecurity is not just about defending the enterprise and its information assets. In many
cases, restructuring parts or all of an enterprise IT environment in the course of strengthening cybersecurity is also an
opportunity for streamlining and optimising IT.
Cybersecurity Governance
Governance over cybersecurity has a much wider scope
than governance over information security, due to the
multiple facets of cybercrime and cyberwarfare. The
cybersecurity governance framework covers enterprise
security, social elements and technology.
any organisations in Europe use ITIL (IT Infrastructure Library) V3 to design, maintain and control their IT service management processes, including those relating to security. If ITIL, COBIT 5 or
M
both are used, further details are available in the Val IT framework, a legacy ISACA product now included in the overall COBIT series.
34
For an example outline of this approach, see Houdart, Jean-Baptiste, EU Cybersecurity Policy: A Model for Global Governance, atlantic-community.org, 6 February 2013, http://www.atlanticcommunity.org/-/eu-cybersecurity-policy-a-model-for-global-governance.
35
Formally described in ISO 22301 and ISO 22313 standards, with informal guidance in the Business Continuity Institute Good Practice Guidelines 2013 Global Edition: A Guide to Global Good
Practice in Business Continuity
36
Formally described in ISO 27031 and ISO 24762 standards (for disaster recovery service providers)
37
The concepts of continuity, resilience and related standards are integrated in many EU-level and national recommendations or draft statutes.
33
16
38
FIGURE
COBIT 5 Enablers
2. Processes
3. Organisational
Stuctures
4. Culture, Ethics
and Behaviour
5. Information
6. Services,
Infrastructure
and Applications
7. People
Skills and
Competencies
Resources
More detail about how to implement cybersecurity governance based on the enabler model is given in ISACAs Transforming Cybersecurity (2013) publication.
17
The other enablers can help enterprises in implementing practical governance steps rather than just providing written
guidance, which still needs to be reflected in daily business. Using the enabler-based approach ensures that the
underlying ideas and objectives of good cybersecurity governance are fully implemented and that no disconnect exists
between senior management thinking and the day-to-day business.
In enabler-based governance, enterprises should look for the potential manifestations of cybersecurity riskwhether it is
through events, near misses or unusual systems behaviourbefore implementing a solution. Existing security solutions
should be systematically analysed and categorised to determine their effectiveness and value.
1. Analyse impact (with a view to business impacts and other, nonfinancial impacts).
Practical guidance and tools for analysing risk in this manner are available
from a number of recognised standards and frameworks, e.g., ISACA
COBIT 5 for Risk and BCI Good Practice Guidelines.43
ee the ENISA guidebook on national cybersecurity strategies: European Network and Information Security Agency (ENISA), National Cyber Security Strategies Practical Guide on Development
S
and Execution, Greece, December 2012.
See http://www.enisa.europa.eu/activities/risk-management/current-risk/risk-management-inventory/glossary.
41
See European Network and Information Security Agency (ENISA), National Cyber Security Strategies Practical Guide on Development and Execution, Greece, December 2012.
42
An overview from a European point of view is given in the ENISA Threat Landscape 2013,at http://www.enisa.europa.eu/activities/risk-management/evolving-threat-environment/enisa-threatlandscape-2013-overview-of-current-and-emerging-cyber-threats.
43
Business Continuity Institute, Good Practice Guidelines 2013 Global Edition: A Guide to Global Good Practice in Business Continuity, England, 2013, www.thebci.org/index.php/resources/thegood-practice-guidelines
39
40
18
ASSESS RISK
44
45
pecifically, the business impace analysis (BIA) approach recommended in ISO 22301 and ISO 22313. Details on practical BIA implementation are available through secondary literature (see the
S
Risk Guidance paper in this series).
For examples, see COBIT 5 for Risk, ISO 31000 on generic risk management and ISO 27005 on information security risk assessment.
19
47
For example, see the ENISA portal on CIIP and resilience at http://www.enisa.europa.eu/activities/Resilience-and-CIIP.
A vast amount of publicly available information from a European perspective is available. See, for example, www.enisa.europa.eu/activities/Resilience-and-CIIP/networks-and-services-resilience/
cloud-computinghttp://en.wikipedia.org/wiki/Cloud_Security_Alliance.
48
See the portal at www.enisa.europa.eu/activities/Resilience-and-CIIP/critical-infrastructure-and-services/scada-industrial-control-systems. Further information is available from ISACA at www.
isaca.org
49
See ISACAs Transforming Cybersecurity publication for an in-depth discussion on management views and motivations, at www.isaca.org/Knowledge-Center/Research/ResearchDeliverables/
Pages/Transforming-Cybersecurity-Using-COBIT-5.aspx.
50
See, for esample, Baud et al. (2014), at www.lexology.com/library/detail.aspx?g=1f872876-3d23-44e7-a8f1-92a9be8d080b, for an overview of selected EU member states.
46
47
20
10
Exploit
Total
Employees Availability
Attack
Probability
Attractiveness
of Target
TOTAL
CHANGE IN
ATTACKS ATTRACTIVENESS
Decreased
Attractiveness
Number of
Internal
Attackers
Increased
Attractiveness
Detected
Attacks
Identified
Vulnerability
Source: The Business Model for Information Security, ISACA, USA, 2010, figure 37
In Europe, systemic concepts in cybersecurity are often found in management systems or life cycle concepts. Examples
include the traditional plan-do-check-act (PDCA) cycle53 and the life cycle around BCM and ITSCM. Enterprises that are
implementing cybersecurity should embed their related programmes into existing management systems. It is particularly
important to align the cybersecurity system of processes, actions and controls with the surrounding (or underlying)
information security management system (ISMS).
52
53
he underlying thoughts are outlined in ISACAs Business Model for Information Security (BMIS) at www.isaca.org/bmis. Enterprises should note that the legacy BMIS has been incorporated into
T
COBIT 5.
The plan-do-check-act (PDCA) (or Deming) cycle is present in most major standards and series of standards, such as ISO 27000 and ISO 22301. The business continuity and IT service continuity
21
Cybersecurity Assurance
Enterprises should establish and maintain reasonable assurance over their cybersecurity activities and initiatives for
GRC. Providing cybersecurity assurance involves the system of enterprise internal controls and the organisational and
logical structures that support the functioning of these controls. Enterprises should implement the following three pillars
of assurance for cybersecurity:
Further details are given in the European Cybersecurity Implementation: Assurance paper in this series.
THREE LINES OF DEFENCE
The first step for implementing
cybersecurity assurance is to determine
and define cybersecurity activities
and controls through the three lines
of defence that are common to most
European and global concepts of control
systems. Figure 11 shows an overview
of these three lines and their assurance
contribution.
In cybersecurity, the first line of defence
managementis often extended to
include customers, business partners,
the general public and the media. The
second linerisk managementis usually
distributed across various ERM functions,
covering non-IT aspects of cybersecurity
and technology. Within the third line
internal auditinvestigative and forensic
activities are often extended to include
external experts or law enforcement.
In the European context, the concept of
three lines of defence is well established
and implemented in most national and EUlevel concepts of cybersecurity.
FIGURE
11
First lineManagement
22
Organisational readiness
Principles, policies and frameworks link directly to the first enabler in the COBIT 5 assurance model. See figure 9.
See COBIT 5 for Assurance for details on control architecture and control design.
An example of a cybersecurity audit programme is provided in the European Cybersecurity Implementation: Audit Programme paper in this series, which can be found at www.isaca.org/EUcyber-implementation
57
There is an ongoing debate on mandatory incident reporting and intervention by public authorities in many European countries.
54
55
56
23
58
59
Details for each of these actions can be found at http://ec.europa.eu/digital-agenda/en/pillar-iii-trust-security/ or by following the link attached to each listed action.
Digital Agenda for Europe is at http://ec.europa.eu/digital-agenda/en/
24
European Commission, Joint Communication to the European Parliament, the Council, the
European Economic and Social Committee and the Committee of the RegionsCybersecurity
Strategy of the European Union: An Open, Safe and Secure Cyberspace, Brussels, 2 July
2013,
http://ec.europa.eu/information_society/newsroom/cf/dae/document.cfm?doc_id=1667
European Network and Information Security Agency (ENISA), National Cyber Security
Strategies Practical Guide on Development and Execution, Greece, December 2012
ENISA, Threat Landscape 2013Overview of current and emerging cyber-threats, Greece,
11 December 2013,
www.enisa.europa.eu/activities/risk-management/evolving-threat-environment/enisa-threat-landscape-2013overview-of-current-and-emerging-cyber-threats
International Auditing and Assurance Standards Board, ISAE 3402 Standard for Reporting
on Controls at Service Organizations
International Organisation for Standardisation (ISO), ISO/IEC 20000-2:2012 Information
technologyService managementPart 2: Guidance on the application of service
management systems
ISO, ISO/IEC 22301:2012 Societal securityBusiness continuity management systems
Requirements
ISO, ISO/IEC 22313:2012 Societal securityBusiness continuity management systems
Guidance
ISO, ISO/IEC 24762:2008 Information technologySecurity techniquesGuidelines for
information and communications technology disaster recovery services
ISO, ISO/IEC 27001:2013 Information technologySecurity techniquesInformation security
management systemsRequirements
ISO, ISO/IEC 27005:2011 Information technologySecurity techniquesInformation security
risk management.
ISO, ISO/IEC 27031:2011 Information technologySecurity techniquesGuidelines for
information and communication technology readiness for business continuity.
25
www.isaca.org/Knowledge-Center/Research/ResearchDeliverables/Pages/Advanced-Persistent-ThreatsAwareness-Study-Results.aspx
www.isaca.org/COBIT/Pages/COBIT-5-Framework-product-page.aspx
www.isaca.org/COBIT/Pages/Assurance-product-page.aspx
www.isaca.org/COBIT/Pages/Information-Security-Product-Page.aspx
www.isaca.org/COBIT/Pages/Risk-product-page.aspx
www.isaca.org/Knowledge-Center/Research/ResearchDeliverables/Pages/Responding-to-Targeted-Cyberattacks.
aspx
www.isaca.org/Knowledge-Center/Research/ResearchDeliverables/Pages/Transforming-Cybersecurity-UsingCOBIT-5.aspx
26