Itron News
Ensuring the Security of the United States’ Bulk-Power System
May 19, 2020
Electricity is essential to our quality of life. In good economies and bad, in times of plenty and times of crisis, when we flip on the light switch, we trust the lights will come on, every time. Behind the scenes, utilities are working hard to safely and reliably deliver that electricity to America, and cyber security is an essential component of their operations and Itron’s.
To prevent the crippling impacts of malicious cyberattacks, President Trump issued an “Executive Order on Securing the United States Bulk-Power System” on May 1, 2020. The executive order (EO) prohibits the procurement of bulk-power electrical equipment subject to the direction of a “foreign adversary.” Details are still unfolding as the U.S. Department of Energy (DOE) plans to issue additional guidance and promulgate regulations for implementing this order over the next 150 days.
For providers of critical infrastructure, this EO should promote investments in cybersecurity and preparedness, which Moody’s Investors Service said is “credit positive” for electric utilities. In fact, Moody claims that this order may incite positive change, encouraging suppliers to invest in cybersecurity practices.
Since this EO could have implications for utilities and electrical equipment providers, Itron is actively tracking this issue and consulting with DOE and various industry trade associations to better understand the order’s jurisdictional reach.
Department of Energy (DOE) Secretary Brouillette has said the Administration “will be looking to leverage domestic manufacturing opportunities as a way to strengthen the security of the bulk-power system.” As a U.S.-based company with domestic manufacturing, Itron does not expect to be significantly impacted by this EO. Generally, what we sell in America, we make in America.
At Itron, we agree that grid security is foundational to the reliable and resilient delivery of electricity in America, and this is an area where we are very focused. Itron works with third-party industry security experts, which has included efforts with DOE’s Idaho National Laboratory, to ensure our products and services are assessed independently for security integrity and cyber resilience.
Reliable access to electricity is a vital service and ensuring the security of the electric grid is more essential now than ever.
We will provide updates on this EO as we learn more over the next 150 days.
To prevent the crippling impacts of malicious cyberattacks, President Trump issued an “Executive Order on Securing the United States Bulk-Power System” on May 1, 2020. The executive order (EO) prohibits the procurement of bulk-power electrical equipment subject to the direction of a “foreign adversary.” Details are still unfolding as the U.S. Department of Energy (DOE) plans to issue additional guidance and promulgate regulations for implementing this order over the next 150 days.
For providers of critical infrastructure, this EO should promote investments in cybersecurity and preparedness, which Moody’s Investors Service said is “credit positive” for electric utilities. In fact, Moody claims that this order may incite positive change, encouraging suppliers to invest in cybersecurity practices.
Since this EO could have implications for utilities and electrical equipment providers, Itron is actively tracking this issue and consulting with DOE and various industry trade associations to better understand the order’s jurisdictional reach.
Department of Energy (DOE) Secretary Brouillette has said the Administration “will be looking to leverage domestic manufacturing opportunities as a way to strengthen the security of the bulk-power system.” As a U.S.-based company with domestic manufacturing, Itron does not expect to be significantly impacted by this EO. Generally, what we sell in America, we make in America.
At Itron, we agree that grid security is foundational to the reliable and resilient delivery of electricity in America, and this is an area where we are very focused. Itron works with third-party industry security experts, which has included efforts with DOE’s Idaho National Laboratory, to ensure our products and services are assessed independently for security integrity and cyber resilience.
Reliable access to electricity is a vital service and ensuring the security of the electric grid is more essential now than ever.
We will provide updates on this EO as we learn more over the next 150 days.
Kesalahan terjadi ketika Memproses Template.
The following has evaluated to null or missing:
==> authorContent.contentFields [in template "44616#44647#114455" at line 9, column 17]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: contentFields = authorContent.content... [in template "44616#44647#114455" at line 9, column 1]
----
1<#assign
2 webContentData = jsonFactoryUtil.createJSONObject(author.getData())
3 classPK = webContentData.classPK
4/>
5
6<#assign
7authorContent = restClient.get("/headless-delivery/v1.0/structured-contents/" + classPK + "?fields=contentFields%2CfriendlyUrlPath%2CtaxonomyCategoryBriefs")
8contentFields = authorContent.contentFields
9categories=authorContent.taxonomyCategoryBriefs
10authorContentData = jsonFactoryUtil.createJSONObject(authorContent)
11friendlyURL = authorContentData.friendlyUrlPath
12authorCategoryId = "0"
13/>
14
15<#list contentFields as contentField >
16 <#assign
17 contentFieldData = jsonFactoryUtil.createJSONObject(contentField)
18 name = contentField.name
19 />
20 <#if name == 'authorImage'>
21 <#if (contentField.contentFieldValue.image)??>
22 <#assign authorImageURL = contentField.contentFieldValue.image.contentUrl />
23 </#if>
24 </#if>
25 <#if name == 'authorName'>
26 <#assign authorName = contentField.contentFieldValue.data />
27 <#list categories as category >
28 <#if authorName == category.taxonomyCategoryName>
29 <#assign authorCategoryId = category.taxonomyCategoryId />
30 </#if>
31 </#list>
32 </#if>
33 <#if name == 'authorDescription'>
34 <#assign authorDescription = contentField.contentFieldValue.data />
35
36 </#if>
37
38 <#if name == 'authorJobTitle'>
39 <#assign authorJobTitle = contentField.contentFieldValue.data />
40
41 </#if>
42
43</#list>
44
45<div class="blog-author-info">
46 <#if authorImageURL??>
47 <img class="blog-author-img" id="author-image" src="${authorImageURL}" alt="" />
48 </#if>
49 <#if authorName??>
50 <#if authorName != "">
51 <p class="blog-author-name">By <a id="author-detail-page" href="/w/${friendlyURL}?filter_category_552298=${authorCategoryId}"><span id="author-full-name">${authorName}</span></a></p>
52 <hr />
53 </#if>
54 </#if>
55 <#if authorJobTitle??>
56 <#if authorJobTitle != "">
57 <p class="blog-author-title" id="author-job-title" >${authorJobTitle}</p>
58 <hr />
59 </#if>
60 </#if>
61 <#if authorDescription??>
62 <#if authorDescription != "" && authorDescription != "null" >
63 <p class="blog-author-desc" id="author-job-desc">${authorDescription}</p>
64 <hr />
65 </#if>
66 </#if>
67</div>
The following has evaluated to null or missing:
==> authorContent.contentFields [in template "44616#44647#114455" at line 9, column 17]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing</#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: contentFields = authorContent.content... [in template "44616#44647#114455" at line 9, column 1]
----
1<#assign
2 webContentData = jsonFactoryUtil.createJSONObject(author.getData())
3 classPK = webContentData.classPK
4/>
5
6<#assign
7authorContent = restClient.get("/headless-delivery/v1.0/structured-contents/" + classPK + "?fields=contentFields%2CfriendlyUrlPath%2CtaxonomyCategoryBriefs")
8contentFields = authorContent.contentFields
9categories=authorContent.taxonomyCategoryBriefs
10authorContentData = jsonFactoryUtil.createJSONObject(authorContent)
11friendlyURL = authorContentData.friendlyUrlPath
12authorCategoryId = "0"
13/>
14
15<#list contentFields as contentField >
16 <#assign
17 contentFieldData = jsonFactoryUtil.createJSONObject(contentField)
18 name = contentField.name
19 />
20 <#if name == 'authorImage'>
21 <#if (contentField.contentFieldValue.image)??>
22 <#assign authorImageURL = contentField.contentFieldValue.image.contentUrl />
23 </#if>
24 </#if>
25 <#if name == 'authorName'>
26 <#assign authorName = contentField.contentFieldValue.data />
27 <#list categories as category >
28 <#if authorName == category.taxonomyCategoryName>
29 <#assign authorCategoryId = category.taxonomyCategoryId />
30 </#if>
31 </#list>
32 </#if>
33 <#if name == 'authorDescription'>
34 <#assign authorDescription = contentField.contentFieldValue.data />
35
36 </#if>
37
38 <#if name == 'authorJobTitle'>
39 <#assign authorJobTitle = contentField.contentFieldValue.data />
40
41 </#if>
42
43</#list>
44
45<div class="blog-author-info">
46 <#if authorImageURL??>
47 <img class="blog-author-img" id="author-image" src="${authorImageURL}" alt="" />
48 </#if>
49 <#if authorName??>
50 <#if authorName != "">
51 <p class="blog-author-name">By <a id="author-detail-page" href="/w/${friendlyURL}?filter_category_552298=${authorCategoryId}"><span id="author-full-name">${authorName}</span></a></p>
52 <hr />
53 </#if>
54 </#if>
55 <#if authorJobTitle??>
56 <#if authorJobTitle != "">
57 <p class="blog-author-title" id="author-job-title" >${authorJobTitle}</p>
58 <hr />
59 </#if>
60 </#if>
61 <#if authorDescription??>
62 <#if authorDescription != "" && authorDescription != "null" >
63 <p class="blog-author-desc" id="author-job-desc">${authorDescription}</p>
64 <hr />
65 </#if>
66 </#if>
67</div>