Assessing Smart Grid Security
Assessing Smart Grid Security
The evolution from traditional power networks to smart grid involves many
aspects including data network transformation, distributed functionality, and
two-way information flow between supplier and customer. Networks are
transforming to the use of packet-based communications and the use of
newer networking technologies, including optical, Internet Protocol (IP) and
Multiprotocol Label Switching (MPLS). Functionality is being distributed to
substations, transmission and distribution nodes, and to the customer site.
Information flow evolves to two-way communication of rating, billing, and
usage data between the customer and supplier (including “smart metering”).
These changes introduce new reliability and security challenges for the
power grid utility company. In the security domain, new threat vectors are
introduced, and vulnerabilities and attacks related to data networking and
information technology become more relevant. Security, reliability, and
availability of the management and control network and functionality are
business critical. This paper describes a methodology for assessing smart grid
security, and trends in smart grid security that we have observed while
applying this methodology. © 2012 Alcatel-Lucent.
Bell Labs Technical Journal 17(3), 87–104 (2012) © 2012 Alcatel-Lucent. Published by Wiley Periodicals, Inc.
Published online in Wiley Online Library (wileyonlinelibrary.com) • DOI: 10.1002/bltj.21560
Panel 1. Abbreviations, Acronyms, and Terms
3G—Third generation LAN—Local area network
3GPP—3rd Generation Partnership Project LTE—Long Term Evolution
AES—Advanced Encryption Standard MAC—Medium access control
AMI—Advanced metering infrastructure MMS—Manufacturing Messaging
AMR—Automatic meter reading Specification
ATM—Asynchronous Transfer Mode MPLS—Multiprotocol Label Switching
BLAS—Bell Labs Advisory Service NAC—Network access control
CCTV—Closed circuit television NAN—Neighborhood area network
CIP—Critical infrastructure protection NERC—North American Electric Reliability
CNCI—Comprehensive National Cybersecurity Corporation
Initiative NIST—National Institute of Standards and
DA—Distribution automation Technology
DES—Data Encryption Standard PTT—Push-to-talk
DHS—Department of Homeland Security SbD—Security by Design
DMZ—Demilitarized zone SCADA—Supervisory control and data
DNP3—Distributed Network Protocol 3 acquisition
DoS—Denial of service SG—Smart grid
DPI—Deep packet inspection SONET—Synchronous Optical Network
DR—Demand response SSL—Secure Sockets Layer
FAN—Field area network TA—Transmission automation
GOOSE—Generic Object Oriented Substation TCP—Transmission Control Protocol
Event TDM—Time Division Multiplexing
HQ—Headquarters TLS—Transport Layer Security
ICCP—Inter-Control Center Communications UMTS—Universal Mobile
Protocol Telecommunications System
ICT—Information and communication U.S. —United States
technology USB—Universal serial bus
IDS—Intrusion detection system VLAN—Virtual local area network
IEC—International Engineering Consortium VLL—Virtual leased line
IED—Intelligent electronic device VPLS—Virtual private LAN service
IP—Internet Protocol VPN—Virtual private network
IPS—Intrusion protection system VPRN—Virtual private routed network
IPsec—Internet Protocol security WAN—Wide area network
ISMS—Information security management WCDMA—Wideband code division multiple
system access
ISO—International Organization for WiMAX—Worldwide Interoperability for
Standardization Microwave Access
ISO27K—ISO 27000 series
a critical requirement, along with reliability and per- and consumers of power [1]. Many utilities are
formance (and, indeed, security issues can threaten reli- transforming their networks to accommodate estab-
ability and performance). lished and emerging applications on a common, inte-
The evolution of the power grid entails upgrad- grated network based on Internet Protocol (IP),
ing the infrastructure to a “smart grid” to support primarily for reasons of cost efficiency and flexibility.
two-way communication between electric genera- The use of IP networking brings the security chal-
tion, transmission and distribution infrastructure, lenges associated with this technology.
transmission lines
substation
Feeder
Figure 1.
Generation, transmission, and distribution in smart grid.
includes policies, training, risk management, compli- time, critical infrastructure presents a particularly
ance, operations security, business continuity plan- attractive target to potential attackers.
ning, and many other aspects. Developing these The smart grid will bring security benefits as well
human-focused procedures takes time—and needs to as security risks. The smart grid continuously monitors
take time—to ensure that it is done correctly. [7] itself to detect unsafe or insecure situations that could
Furthermore, many (if not most) of the larger utility detract from its reliability and safe operation [7].
companies will have significant in-house development Security Goals
or integration—so supply chain security and applica- Key goals for security include reducing risks and
tion security are crucial. Many will use data centers costs. Generally, security is significantly less costly if it
and call centers, and may be consolidating and evolv- is addressed at early stages (requirements, architec-
ing to the use of virtualization and migration to cloud- ture, design) of systems development rather than
based deployment models. Utility companies also being added in later stages. The principle of “Security
have a significant mobile workforce, requiring secure by Design” (or SbD) is well established, and seeks to
communications while in the field. The range of secu- provide a framework for addressing security from the
rity aspects to be addressed by a smart grid utility outset, in the initial phases of development.
company are very broad, and some aspects are rela- Security is essentially about risk management.
tively new and still rapidly evolving. The level of security employed should be driven by
the level of risk—where risk includes both the likeli-
Smart Grid Security Issues hood and the impact of an attack. There are risks asso-
Security for critical infrastructure (including util- ciated with compromising the confidentiality,
ity companies) is a very broad concern and involves integrity, and availability of information and services.
many aspects including: A key goal of security management should be to
• Physical security of plant, equipment, and net- reduce the costs associated with security. This includes
works. the cost of security itself, and the costs associated with
• Cyber security for networking and computing. security breaches. Costs associated with security
• Security management for the corporation or include;
enterprise itself. • Personnel costs,
• Specific security issues for supervisory and control • Appliance costs,
applications and networks (SCADA). • Software costs,
• Specific security issues for endpoints (including • Administrative costs, and
intelligent electronic devices (IEDs) and meters). • Costs associated with security breaches.
The evolution to a smart grid increases the focus on Security management involves balancing the cost
security. The smart grid will be characterized by a two- of security against the cost of security breaches, based
way flow of electricity and information [7] and the use on risk assessment of breaches, taking into account
of communications and distributed computing. The their likelihood and impact. Costs increase as com-
smart grid can also be characterized as “a network of plexity increases in conjunction with the prolifera-
networks.” These aspects introduce new threat vectors, tion of equipment and inconsistencies among device
compared with legacy electricity networks. The con- types and software versions.
vergence of the information and communications No security solution can be absolute. There are
infrastructure with the electric power grid introduces always potential ways to contravene any security con-
new security and privacy-related challenges [23]. As trol, especially since complex systems can have
utilities continue to leverage information technology, unknown as well as known vulnerabilities. To com-
especially for the smart grid, they also expose their pensate for this, most enterprises (including power
infrastructure to all of the risks and threats associated grid utility companies) will generally employ the
with information technology in general. At the same “defense-in-depth” principle, and implement multiple
Tools analysis
Architecture assessment
Assess results from
Assess use of technical
test/audit tools, e.g.,
security enablers such as
Utility penetration testing,
firewalls, IPS, AAA,
networks vulnerability scanning,
encryption, DMZ, and
offline configuration,
VPN.
and auditing.
Baseline assessment
Evaluate the target against a range of authoritative standards, recommendations, and
best practices pertinent to the domain, e.g., NIST, ISO, NERC CIP.
Figure 2.
Overview of assessment methodology.
3. Understanding the threats that the critical assets threats include theft of content, denial of service, eaves-
are exposed to. dropping, and unauthorized disclosure of information.
4. Recognizing potential vulnerabilities and con- When defining business risk, it is useful to consider the
firming known vulnerabilities. threat agents and threat vectors (the avenues by which
5. Prioritizing the vulnerabilities, based on their a threat may be realized). For critical infrastructure,
associated risk. potential threat agents could include company employ-
6. Determining the countermeasures needed to ees, terrorists, espionage agents, extortionists, hackers,
thwart the key vulnerabilities. cyber-criminals, customers, and outsourced mainte-
7. Performing a business impact analysis to deter- nance staff. Potential threat vectors (or potential chan-
mine when or if to develop the security features nels of attack) could include the Internet, wireless
needed to implement the countermeasures. access points, the enterprise intranet, mobile devices
The first task that is performed in a threat analysis (including USB devices), remote endpoints (including
is to define the business risk, which is the business meters), the supply chain, and the company’s own sys-
threat environment surrounding a product or solution tems development organization. Several sources may
when it is deployed in the production environment. A be consulted to identify business threats that will be
business threat is defined as an adversary’s goal or present in the deployed environment. These can
motive for attacking the business or organization. To include industry consortia or regulations for the prod-
prevent the business threat from being realized, pro- uct or solution, customer vertical industries (e.g., finan-
tective measures must be in place. Example business cial, healthcare, manufacturing), standards bodies that
GENERATION
OPTIC IP/MPLS Threats/attacks: Eavesdropping,
unauthorized access
Countermeasures: Mutual authentication,
domain-specific protocol security (e.g., IEC
4G-LTE
WiMAX 62351)
INTEGRATED
3G RENEWABLE
TRANSMISSION PMR/LMR
SM
AR
TC
ITY
MICRO
FTTH GENERATION
DISTRIBUTION PLC
Threats/attacks: Unauthorized access
Radio + Threats/attacks: Theft of service, meter hacking, tampering,
Countermeasures: Physical security, secure −
management interfaces, role-based access control ELECTRIC ENERGY cloning
VEHICLE STORAGE Countermeasures: Mutual authentication, tamper-proof
hardware, encryption, secure-boot, remote management,
remote attestation
Figure 3.
Example threats, attacks, and candidate countermeasures.
are derived from authoritative work by industry be used to select the appropriate sources, to filter the
bodies (e.g., the National Institute of Standards and resources for applicability, and to prioritize the con-
Technology (NIST), ISO, and NERC) and against the trols. The baseline controls can be used in an explicit
Bell Labs security knowledge base. and formal manner, to survey the target for compli-
Below, we describe some sources of best practices ance. Alternatively, a less-formal approach can be
or baseline security requirements in the public taken, using the knowledge base to structure the dia-
domain. Some of these are specific to the United logue with the target of the assessment, and as a ref-
States, but are nevertheless relevant references for erence for grounding findings and recommendations.
assessments of any target regardless of the jurisdic- Tools Analysis
tion of deployment. The tools analysis component of the assessment
In [22], the United States National Institute of methodology involves the use of tools to audit or test
Standards and Technology (NIST) specifies security the systems and networks of the target. Tools can be
controls for Smart Grid Cyber Security, based on secu- active or passive, online or offline. A wide range of
rity controls defined in [25] (originally for U.S. federal potential tools could be brought to bear on the target.
information systems generally, but considered to be Offline configuration analysis tools can audit the con-
more broadly applicable). figuration of network devices or systems for vulnera-
The North American Electric Reliability Corporation bilities. Vulnerability scanning tools can scan and
(NERC) specifies a high-level set of security controls in probe systems and networking devices. Tools can be
[18] that are specifically written for critical infra- used to simulate different types of denial of service
structure. Eight security standards are included, with attacks at different layers of the communications pro-
110 requirements. tocol stack. For application layer protocols, whether
A wide-ranging set of 133 security controls for domain-specific (e.g., SCADA protocols) or general
information security management systems (ISMS) are (e.g., Web protocols), protocol flooding and fuzzing
specified by the International Organization for tools can be employed to stress the robustness of the
Standardization (ISO) and International Electrotechnical protocol implementation. Protocol fuzzing tools delib-
Commission (IEC) in [12]. erately subject the target to malformed protocol mes-
The U.S. Department of Homeland Security sages to try to provoke errors that may crash the
(DHS) specified a catalog of controls for critical infra- device, impair its performance, or even potentially
structure control systems in [27]. allow execution of arbitrary code for a more precise
The U.S. Comprehensive National Cybersecurity attack.
Initiative (CNCI) has derived a set of 20 high level If the target of an assessment is an operational
controls based on a prioritization of [25] from NIST. network or enterprise, there will generally be judi-
Bell Labs maintains a knowledge base of security cious constraints on the types of tools that can be
controls, best practices, and baseline security require- employed and the rules of engagement—obviously
ments including over 800 at the product level and any risk to the service should be avoided, and the
over 70 higher-level requirements for solution tools themselves can be considered a security risk.
deployments. These are a wide-ranging set of best When the target is a pre-deployment configuration
practices for broad coverage and wide applicability in a testing environment, potentially there is scope
across all Alcatel-Lucent products, and many are for use of a wider range of tools, including more active
applicable to products that are relevant for use in criti- and aggressive options that endeavor to actually pene-
cal infrastructure deployments. trate or impair the target.
Considered in aggregate, the references above
represent a very large set of potential controls or best Architecture Assessment
practices to consider, which offer a high degree of The architecture assessment component of the
overlap between the sources. Expert judgement can assessment methodology can be a more informal and