ML19100A007: Difference between revisions
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
||
| Line 1: | Line 1: | ||
{{Adams | |||
| number = ML19100A007 | |||
| issue date = 04/10/2019 | |||
| title = Information Request for the Cyber-Security Baseline Security Inspection, Notification to Perform Inspection 05000348/2019013; 05000364/201901 | |||
| author name = Shaeffer S | |||
| author affiliation = NRC/RGN-II/DRS/EB2 | |||
| addressee name = Kharrl C | |||
| addressee affiliation = Southern Nuclear Operating Co, Inc | |||
| docket = 05000348, 05000364 | |||
| license number = NPF-002, NPF-008 | |||
| contact person = | |||
| document report number = IR 2019013 | |||
| document type = Inspection Plan, Letter | |||
| page count = 9 | |||
}} | |||
See also: [[see also::IR 05000364/2019001]] | |||
=Text= | |||
{{#Wiki_filter:UNITED STATES | |||
NUCLEAR REGULATORY COMMISSION | |||
REGION II | |||
245 PEACHTREE CENTER AVENUE NE, SUITE 1200 | |||
ATLANTA, GEORGIA 30303-1257 | |||
April 10, 2019 | |||
Mr. Charles Kharrl | |||
Southern Nuclear Operating Co., Inc. | |||
Joseph M. Farley Nuclear Plant | |||
7388 North State Highway 95 | |||
Columbia, AL 36319 | |||
SUBJECT: JOSEPH M. FARLEY NUCLEAR PLANT - INFORMATION REQUEST FOR | |||
THE CYBER-SECURITY BASELINE SECURITY INSPECTION, | |||
NOTIFICATION TO PERFORM INSPECTION 05000348/2019013; | |||
05000364/2019013 | |||
Dear Mr. Kharrl: | |||
On August 12, 2019, the U.S. Nuclear Regulatory Commission (NRC) will begin a baseline | |||
inspection in accordance with Inspection Procedure (IP) 71130.10P Cyber-Security, | |||
Revision 0 at Farley Nuclear Plant, Units 1 and 2. The inspection will be performed to | |||
evaluate and verify your ability to meet the Milestone 8 (i.e., full implementation) requirements | |||
of the NRCs Cyber-Security Rule, Title 10, Code of Federal Regulations (CFR), Part 73, | |||
Section 54, | |||
Protection of Digital Computer and Communication Systems and Networks. The onsite portion | |||
of the inspection will take place during the weeks of August 12, 2019, and August 26, 2019. | |||
Experience has shown that baseline inspections are extremely resource intensive, both for the | |||
NRC inspectors and the licensee staff. In order to minimize the inspection impact on the site | |||
and to ensure a productive inspection for both parties, we have enclosed a request for | |||
documents needed for the inspection. These documents have been divided into four groups. | |||
The first group specifies information necessary to assist the inspection team in choosing the | |||
focus areas (i.e., sample set) to be inspected by the cyber-security IP. This information should | |||
be made available via secure site (i.e., Sharepoint, Certrec) no later than June 10, 2019. | |||
The inspection team will review this information and, by July 1, 2019, will request the | |||
specific items that should be provided for review. | |||
The second group of additional requested documents will assist the inspection team in the | |||
evaluation of the critical systems and critical digital assets (CSs/CDAs), defensive architecture, | |||
and the areas of the licensees CSP selected for the cyber-security inspection. This information | |||
will be requested for review via secure site (i.e., Sharepoint, Certrec) before July 15, 2019. | |||
The third group of requested documents consists of those items that the inspection team will | |||
review, or need access to, during the inspection. Please have this information available by the | |||
first day of the onsite inspection, August 12, 2019. | |||
C. Kharrl 2 | |||
The fourth group of information is necessary to aid the inspection team in tracking issues | |||
identified as a result of the inspection. It is requested that this information be provided to the | |||
lead inspector as the information is generated during the inspection. It is important that all of | |||
these documents are up to date and complete in order to minimize the number of additional | |||
documents requested during the preparation and/or the onsite portions of the inspection. | |||
The lead inspector for this inspection is David Strickland. We understand that our regulatory | |||
contact for this inspection is Gene Surber of your organization. If there are any questions about | |||
the inspection or the material requested, please contact the lead inspector at 404-997-4440 or | |||
via e-mail at David.Strickland@nrc.gov. | |||
This letter does not contain new or amended information collection requirements subject to the | |||
Paperwork Reduction Act of 1995 (44 U.S.C. 3501 et seq.). Existing information collection | |||
requirements were approved by the Office of Management and Budget, control number 3150- | |||
0011. The NRC may not conduct or sponsor, and a person is not required to respond to a | |||
request for information or an information collection requirement unless the requesting document | |||
displays a currently valid Office of Management and Budget control number. | |||
In accordance with 10 CFR 2.390, Public Inspections, Exemptions, Requests for Withholding, | |||
of the NRC's "Rules of Practice," a copy of this letter and its enclosure will not be available | |||
electronically for public inspection in the NRCs Public Document Room or from the Publicly | |||
Available Records (PARS) component of the NRC's Agencywide Documents Access and | |||
Management System (ADAMS). ADAMS is accessible from the NRC Web site at | |||
http://www.nrc.gov/reading-rm/adams.html (the Public Electronic Reading Room). | |||
Sincerely, | |||
/RA/ | |||
Scott M. Shaeffer, Chief | |||
Engineering Branch 2 | |||
Division of Reactor Safety | |||
Docket Nos. 50-348; 50-364 | |||
License Nos. NPF-2; NPF-8 | |||
Enclosure: | |||
Security Inspection Document Request | |||
cc: See Page 3 | |||
C. Kharrl 3 | |||
cc: | |||
Cyneetha Evans | |||
Site Security Manager | |||
Joseph M. Farley Nuclear Plant | |||
7388 North State Highway 95 | |||
Columbia, AL 36319 | |||
_ML 19100A007_ SUNSI REVIEW COMPLETE FORM 665 ATTACHED | |||
OFFICE RII/DRS/EB2 RII/DRS/EB2 | |||
SIGNATURE DWS5 SMS | |||
NAME D.STRICKLAND S.SHAEFFER | |||
DATE 4/ 9 /2019 4/ 10 / 2019 | |||
E-MAIL COPY? YES NO YES NO | |||
Inspection Report: 05000348/2019013; 05000364/2019013 | |||
Inspection Dates: Weeks of August 12, 2019, and August 26, 2019 | |||
Inspection Procedure: IP 71130.10P, Cyber-Security, Revision 0 | |||
Reference: ML17156A215, Guidance Document for Development of the | |||
Request for Information (RFI) and Notification Letter for | |||
Full-Implementation of the Cyber-Security Inspection, Revision 0 | |||
NRC Inspectors: David Strickland, Lead Larry Jones | |||
404-997-4440 404-997-4837 | |||
David.Strickland@nrc.gov Larry.Jones@nrc.gov | |||
NRC Contractors: Alan Konkal Alexander Prada | |||
Alan.Konkal@nrc.gov Alexander.Prada@nrc.gov | |||
I. Information Requested for In-Office Preparation | |||
The initial request for information (i.e., first RFI) concentrates on providing the inspection | |||
team with the general information necessary to select appropriate components and CSP | |||
elements to develop a site-specific inspection plan. The first RFI is used to identify the | |||
list of critical systems and critical digital assets (CSs/CDAs) plus operational and | |||
management (O&M) security control portions of the CSP to be chosen as the sample | |||
set required to be inspected by the cyber-security IP. The first RFIs requested | |||
information is specified below in Table RFI #1. The Table RFI #1 information is | |||
requested to be provided by, June 10, 2019 or sooner, to facilitate the selection of the | |||
specific items that will be reviewed during the onsite inspection weeks. | |||
The inspection team will examine the returned documentation from the first RFI and | |||
identify/select specific systems and equipment (e.g., CSs/CDAs) to provide a more | |||
focused follow-up request to develop the second RFI. The inspection team will submit | |||
the specific systems and equipment list to your staff by July 1, 2019, which will identify | |||
the specific systems and equipment that will be utilized to evaluate the CSs/CDAs, | |||
defensive architecture, and the areas of the licensees CSP selected for the cyber- | |||
security inspection. We request that the additional information provided from the second | |||
RFI be made available by July 15, 2019. All requests for information shall follow the | |||
guidance document ML17156A215 referenced above. | |||
Enclosure | |||
2 | |||
The required Table RFI 1 information shall be provided via secure site (i.e., Sharepoint, | |||
Certrec) by June 10, 2019. The preferred file format for all lists is object character | |||
recognition (OCR) readable or a searchable Excel spreadsheet file. These files should | |||
be indexed and hyper-linked to facilitate ease of use. If you have any questions | |||
regarding this information, please call the inspection team leader as soon as possible. | |||
Table RFI #1 | |||
Section 3, Paragraph Number/Title: Items | |||
1 List All Identified Critical Systems and Critical Digital Assets All | |||
List CDA Facility and Site Ethernet - Transmission Control All | |||
2 Protocol/Internet Protocol (TCP/IP) based Local Area Networks (LANs) | |||
and identify those LANs that have non-CDAs on them | |||
List CDA facility and site non-ethernet TCP/IP based LANs including All | |||
3 those industrial networks and identify LANs that have non-CDAs on | |||
them | |||
4 Network Topology Diagrams (be sure to include all NIDS and SIEMs All | |||
for EP networks and Security level 3 and 4 networks) | |||
8 List all network security boundary devices for EP networks and all All | |||
network security boundary devices for levels 3 and 4 | |||
9 List CDA wireless Industrial networks All | |||
11 Network intrusion detection system documentation for Critical Systems (11.a.1) | |||
that have CDAs associated with them (11.a.) | |||
12 Security Information and Event Management (SIEM) documentation (12.a.1) | |||
for Critical systems that have CDAs associated with them (12.a.2) | |||
14 List EP and Security onsite and offsite digital communication systems All | |||
25 Cyber-Security Assessment and Cyber-Security Incident Response All | |||
Teams | |||
28 Copy of Current Cyber Security Plan and copy of any 50.54(p) All | |||
analysis to support changes to the plan | |||
In addition to the above information please provide the following: | |||
(1) Electronic copy of the UFSAR and technical specifications. | |||
(2) Name(s) and phone numbers for the regulatory and technical contacts. | |||
Based on this information, the inspection team will identify and select specific systems | |||
and equipment (e.g., CSs/CDAs) from the information requested by Table RFI #1 and | |||
submit a list of specific systems and equipment to your staff by July 1, 2019 for the | |||
second RFI (i.e., RFI #2). | |||
3 | |||
II. Additional Information Requested to be Available Prior to Inspection. | |||
As stated in Section I above, the inspection team will examine the returned | |||
documentation requested from Table RFI #1 and submit the list of specific systems and | |||
equipment to your staff by July 1, 2019 for the second RFI (i.e., RFI #2). The second | |||
RFI will request additional information required to evaluate the CSs/CDAs, defensive | |||
architecture, and the areas of the licensees CSP selected for the cyber- security | |||
inspection. The additional information requested for the specific systems and | |||
equipment is identified in Table RFI #2. All requested information shall follow the | |||
guidance document ML17156A215 referenced above. | |||
The Table RFI 2 information shall be provided on secure site (i.e., Sharepoint or Certrec) | |||
by July 15, 2019. The preferred file format for all lists is object character recognition | |||
(OCR) readable or a searchable Excel spreadsheet file. These files should be indexed | |||
and hyper-linked to facilitate ease of use. If you have any questions regarding this | |||
information, please call the inspection team leader as soon as possible. | |||
Table RFI #2 | |||
Section 3, | |||
Paragraph Number/Title: Items | |||
5 Plant Computer System Block Diagram (if Plant Computer System is All | |||
selected for inspection) | |||
6 Plant Security System Block Diagram (if Security Computer System is All | |||
selected for inspection) | |||
7 Systems that are distributed Block Diagrams (for systems selected for All | |||
inspection) | |||
10 Host-Based Intrusion Detection System Documentation (for CDAs for (10.a.1) | |||
systems selected for inspection) (10.a.2) | |||
13 List all Maintenance and Test Equipment (M&TE) used on CDAs for All | |||
systems selected for inspection | |||
15 Configuration Management All | |||
16 Supply Chain Management (16.a) | |||
(16.b.1) | |||
(16.b.6) | |||
(16.b.5) | |||
4 | |||
Table RFI #2 | |||
Section 3, | |||
Paragraph Number/Title: Items | |||
17 Portable Media and Mobile Device Control All | |||
18 Software Management All | |||
20 Vendor Access and Monitoring All | |||
21 Work Control All | |||
22 Device Access and Key Control All | |||
23 Password/Authenticator Policy All | |||
24 User Account/Credential Policy All | |||
26 Corrective Actions since last NRC inspection All | |||
27 Cyber-Security Assessments for Selected Systems All | |||
III. Information Requested to be Available on First Day of Inspection | |||
For the specific systems and equipment identified in Section II above, provide the | |||
following RFI (i.e., Table 1ST Week Onsite) by August 12, 2019, the first day of the | |||
inspection. All requested information shall follow the guidance document ML17156A215 | |||
referenced above. | |||
The preferred file format for all lists is object character recognition (OCR) readable or a | |||
searchable Excel spreadsheet file. These files should be indexed and hyper-linked to | |||
facilitate ease of use. If you have any questions regarding this information, please call | |||
the inspection team leader as soon as possible. | |||
5 | |||
Table 1st Week Onsite | |||
Section 3, | |||
Paragraph Number/Title: Items | |||
10 Host-Based Intrusion Detection System Documentation (for CDAs (10.a.3) | |||
for systems selected for inspection) thru | |||
(10.a.12) | |||
11 Network Intrusion Detection System Documentation for Critical (11.a.3) | |||
Systems that have CDAs associated with them thru | |||
(11.a.15) | |||
12 Security Information and Event Management (SIEM) Documentation (12.a.3) | |||
for Critical Systems that have CDAs associated with them thru | |||
(12.a.14) | |||
16 Supply Chain Management (16.b.2) | |||
(6.b.3) | |||
(16.b.4) | |||
19 Cyber-Security Event Notifications All | |||
In addition to the above information please provide the following: | |||
(1) Copies of the following documents do not need to be solely available to the | |||
inspection team as long as the inspectors have easy and unrestrained access | |||
to them. | |||
a. Updated Final Safety Analysis Report, if not previously provided; | |||
b. Original FSAR Volumes; | |||
c. Original SER and Supplements; | |||
d. FSAR Question and Answers; | |||
e. Quality Assurance Plan; | |||
f. Technical Specifications, if not previously provided; | |||
g. Latest IPE/PRA Report; and | |||
h. Vendor Manuals, for applicable systems selected | |||
(2) Assessment and Corrective Actions: | |||
a. The most recent Cyber-Security Quality Assurance (QA) audit and/or | |||
self-assessment; and | |||
b. The last 73.55(m) assessment performed; and | |||
c. Corrective action documents (e.g., condition reports, including status of | |||
corrective actions) generate as a result of the most recent Cyber-Security | |||
Quality Assurance (QA) audit and/or self-assessment. | |||
IV. Information Requested To Be Provided Throughout the Inspection | |||
(1) Copies of any corrective action documents generated as a result of the | |||
inspection teams questions or queries during the inspection. | |||
(2) Copies of the list of questions submitted by the inspection team members and | |||
the status/resolution of the information requested (provided daily during the | |||
inspection to each inspection team member). | |||
If you have any questions regarding the information requested, please contact the inspection | |||
team. | |||
}} | |||
Revision as of 04:38, 2 November 2019
| ML19100A007 | |
| Person / Time | |
|---|---|
| Site: | Farley |
| Issue date: | 04/10/2019 |
| From: | Scott Shaeffer NRC/RGN-II/DRS/EB2 |
| To: | Kharrl C Southern Nuclear Operating Co |
| References | |
| IR 2019013 | |
| Download: ML19100A007 (9) | |
See also: IR 05000364/2019001
Text
UNITED STATES
NUCLEAR REGULATORY COMMISSION
REGION II
245 PEACHTREE CENTER AVENUE NE, SUITE 1200
ATLANTA, GEORGIA 30303-1257
April 10, 2019
Mr. Charles Kharrl
Southern Nuclear Operating Co., Inc.
Joseph M. Farley Nuclear Plant
7388 North State Highway 95
Columbia, AL 36319
SUBJECT: JOSEPH M. FARLEY NUCLEAR PLANT - INFORMATION REQUEST FOR
THE CYBER-SECURITY BASELINE SECURITY INSPECTION,
NOTIFICATION TO PERFORM INSPECTION 05000348/2019013;
Dear Mr. Kharrl:
On August 12, 2019, the U.S. Nuclear Regulatory Commission (NRC) will begin a baseline
inspection in accordance with Inspection Procedure (IP) 71130.10P Cyber-Security,
Revision 0 at Farley Nuclear Plant, Units 1 and 2. The inspection will be performed to
evaluate and verify your ability to meet the Milestone 8 (i.e., full implementation) requirements
of the NRCs Cyber-Security Rule, Title 10, Code of Federal Regulations (CFR), Part 73,
Section 54,
Protection of Digital Computer and Communication Systems and Networks. The onsite portion
of the inspection will take place during the weeks of August 12, 2019, and August 26, 2019.
Experience has shown that baseline inspections are extremely resource intensive, both for the
NRC inspectors and the licensee staff. In order to minimize the inspection impact on the site
and to ensure a productive inspection for both parties, we have enclosed a request for
documents needed for the inspection. These documents have been divided into four groups.
The first group specifies information necessary to assist the inspection team in choosing the
focus areas (i.e., sample set) to be inspected by the cyber-security IP. This information should
be made available via secure site (i.e., Sharepoint, Certrec) no later than June 10, 2019.
The inspection team will review this information and, by July 1, 2019, will request the
specific items that should be provided for review.
The second group of additional requested documents will assist the inspection team in the
evaluation of the critical systems and critical digital assets (CSs/CDAs), defensive architecture,
and the areas of the licensees CSP selected for the cyber-security inspection. This information
will be requested for review via secure site (i.e., Sharepoint, Certrec) before July 15, 2019.
The third group of requested documents consists of those items that the inspection team will
review, or need access to, during the inspection. Please have this information available by the
first day of the onsite inspection, August 12, 2019.
C. Kharrl 2
The fourth group of information is necessary to aid the inspection team in tracking issues
identified as a result of the inspection. It is requested that this information be provided to the
lead inspector as the information is generated during the inspection. It is important that all of
these documents are up to date and complete in order to minimize the number of additional
documents requested during the preparation and/or the onsite portions of the inspection.
The lead inspector for this inspection is David Strickland. We understand that our regulatory
contact for this inspection is Gene Surber of your organization. If there are any questions about
the inspection or the material requested, please contact the lead inspector at 404-997-4440 or
via e-mail at David.Strickland@nrc.gov.
This letter does not contain new or amended information collection requirements subject to the
Paperwork Reduction Act of 1995 (44 U.S.C. 3501 et seq.). Existing information collection
requirements were approved by the Office of Management and Budget, control number 3150-
0011. The NRC may not conduct or sponsor, and a person is not required to respond to a
request for information or an information collection requirement unless the requesting document
displays a currently valid Office of Management and Budget control number.
In accordance with 10 CFR 2.390, Public Inspections, Exemptions, Requests for Withholding,
of the NRC's "Rules of Practice," a copy of this letter and its enclosure will not be available
electronically for public inspection in the NRCs Public Document Room or from the Publicly
Available Records (PARS) component of the NRC's Agencywide Documents Access and
Management System (ADAMS). ADAMS is accessible from the NRC Web site at
http://www.nrc.gov/reading-rm/adams.html (the Public Electronic Reading Room).
Sincerely,
/RA/
Scott M. Shaeffer, Chief
Engineering Branch 2
Division of Reactor Safety
Docket Nos. 50-348; 50-364
Enclosure:
Security Inspection Document Request
cc: See Page 3
C. Kharrl 3
cc:
Cyneetha Evans
Site Security Manager
Joseph M. Farley Nuclear Plant
7388 North State Highway 95
Columbia, AL 36319
_ML 19100A007_ SUNSI REVIEW COMPLETE FORM 665 ATTACHED
OFFICE RII/DRS/EB2 RII/DRS/EB2
SIGNATURE DWS5 SMS
NAME D.STRICKLAND S.SHAEFFER
DATE 4/ 9 /2019 4/ 10 / 2019
E-MAIL COPY? YES NO YES NO
Inspection Report: 05000348/2019013; 05000364/2019013
Inspection Dates: Weeks of August 12, 2019, and August 26, 2019
Inspection Procedure: IP 71130.10P, Cyber-Security, Revision 0
Reference: ML17156A215, Guidance Document for Development of the
Request for Information (RFI) and Notification Letter for
Full-Implementation of the Cyber-Security Inspection, Revision 0
NRC Inspectors: David Strickland, Lead Larry Jones
404-997-4440 404-997-4837
David.Strickland@nrc.gov Larry.Jones@nrc.gov
NRC Contractors: Alan Konkal Alexander Prada
Alan.Konkal@nrc.gov Alexander.Prada@nrc.gov
I. Information Requested for In-Office Preparation
The initial request for information (i.e., first RFI) concentrates on providing the inspection
team with the general information necessary to select appropriate components and CSP
elements to develop a site-specific inspection plan. The first RFI is used to identify the
list of critical systems and critical digital assets (CSs/CDAs) plus operational and
management (O&M) security control portions of the CSP to be chosen as the sample
set required to be inspected by the cyber-security IP. The first RFIs requested
information is specified below in Table RFI #1. The Table RFI #1 information is
requested to be provided by, June 10, 2019 or sooner, to facilitate the selection of the
specific items that will be reviewed during the onsite inspection weeks.
The inspection team will examine the returned documentation from the first RFI and
identify/select specific systems and equipment (e.g., CSs/CDAs) to provide a more
focused follow-up request to develop the second RFI. The inspection team will submit
the specific systems and equipment list to your staff by July 1, 2019, which will identify
the specific systems and equipment that will be utilized to evaluate the CSs/CDAs,
defensive architecture, and the areas of the licensees CSP selected for the cyber-
security inspection. We request that the additional information provided from the second
RFI be made available by July 15, 2019. All requests for information shall follow the
guidance document ML17156A215 referenced above.
Enclosure
2
The required Table RFI 1 information shall be provided via secure site (i.e., Sharepoint,
Certrec) by June 10, 2019. The preferred file format for all lists is object character
recognition (OCR) readable or a searchable Excel spreadsheet file. These files should
be indexed and hyper-linked to facilitate ease of use. If you have any questions
regarding this information, please call the inspection team leader as soon as possible.
Table RFI #1
Section 3, Paragraph Number/Title: Items
1 List All Identified Critical Systems and Critical Digital Assets All
List CDA Facility and Site Ethernet - Transmission Control All
2 Protocol/Internet Protocol (TCP/IP) based Local Area Networks (LANs)
and identify those LANs that have non-CDAs on them
List CDA facility and site non-ethernet TCP/IP based LANs including All
3 those industrial networks and identify LANs that have non-CDAs on
them
4 Network Topology Diagrams (be sure to include all NIDS and SIEMs All
for EP networks and Security level 3 and 4 networks)
8 List all network security boundary devices for EP networks and all All
network security boundary devices for levels 3 and 4
9 List CDA wireless Industrial networks All
11 Network intrusion detection system documentation for Critical Systems (11.a.1)
that have CDAs associated with them (11.a.)
12 Security Information and Event Management (SIEM) documentation (12.a.1)
for Critical systems that have CDAs associated with them (12.a.2)
14 List EP and Security onsite and offsite digital communication systems All
25 Cyber-Security Assessment and Cyber-Security Incident Response All
Teams
28 Copy of Current Cyber Security Plan and copy of any 50.54(p) All
analysis to support changes to the plan
In addition to the above information please provide the following:
(1) Electronic copy of the UFSAR and technical specifications.
(2) Name(s) and phone numbers for the regulatory and technical contacts.
Based on this information, the inspection team will identify and select specific systems
and equipment (e.g., CSs/CDAs) from the information requested by Table RFI #1 and
submit a list of specific systems and equipment to your staff by July 1, 2019 for the
3
II. Additional Information Requested to be Available Prior to Inspection.
As stated in Section I above, the inspection team will examine the returned
documentation requested from Table RFI #1 and submit the list of specific systems and
equipment to your staff by July 1, 2019 for the second RFI (i.e., RFI #2). The second
RFI will request additional information required to evaluate the CSs/CDAs, defensive
architecture, and the areas of the licensees CSP selected for the cyber- security
inspection. The additional information requested for the specific systems and
equipment is identified in Table RFI #2. All requested information shall follow the
guidance document ML17156A215 referenced above.
The Table RFI 2 information shall be provided on secure site (i.e., Sharepoint or Certrec)
by July 15, 2019. The preferred file format for all lists is object character recognition
(OCR) readable or a searchable Excel spreadsheet file. These files should be indexed
and hyper-linked to facilitate ease of use. If you have any questions regarding this
information, please call the inspection team leader as soon as possible.
Table RFI #2
Section 3,
Paragraph Number/Title: Items
5 Plant Computer System Block Diagram (if Plant Computer System is All
selected for inspection)
6 Plant Security System Block Diagram (if Security Computer System is All
selected for inspection)
7 Systems that are distributed Block Diagrams (for systems selected for All
inspection)
10 Host-Based Intrusion Detection System Documentation (for CDAs for (10.a.1)
systems selected for inspection) (10.a.2)
13 List all Maintenance and Test Equipment (M&TE) used on CDAs for All
systems selected for inspection
15 Configuration Management All
16 Supply Chain Management (16.a)
(16.b.1)
(16.b.6)
(16.b.5)
4
Table RFI #2
Section 3,
Paragraph Number/Title: Items
17 Portable Media and Mobile Device Control All
18 Software Management All
20 Vendor Access and Monitoring All
21 Work Control All
22 Device Access and Key Control All
23 Password/Authenticator Policy All
24 User Account/Credential Policy All
26 Corrective Actions since last NRC inspection All
27 Cyber-Security Assessments for Selected Systems All
III. Information Requested to be Available on First Day of Inspection
For the specific systems and equipment identified in Section II above, provide the
following RFI (i.e., Table 1ST Week Onsite) by August 12, 2019, the first day of the
inspection. All requested information shall follow the guidance document ML17156A215
referenced above.
The preferred file format for all lists is object character recognition (OCR) readable or a
searchable Excel spreadsheet file. These files should be indexed and hyper-linked to
facilitate ease of use. If you have any questions regarding this information, please call
the inspection team leader as soon as possible.
5
Table 1st Week Onsite
Section 3,
Paragraph Number/Title: Items
10 Host-Based Intrusion Detection System Documentation (for CDAs (10.a.3)
for systems selected for inspection) thru
(10.a.12)
11 Network Intrusion Detection System Documentation for Critical (11.a.3)
Systems that have CDAs associated with them thru
(11.a.15)
12 Security Information and Event Management (SIEM) Documentation (12.a.3)
for Critical Systems that have CDAs associated with them thru
(12.a.14)
16 Supply Chain Management (16.b.2)
(6.b.3)
(16.b.4)
19 Cyber-Security Event Notifications All
In addition to the above information please provide the following:
(1) Copies of the following documents do not need to be solely available to the
inspection team as long as the inspectors have easy and unrestrained access
to them.
a. Updated Final Safety Analysis Report, if not previously provided;
b. Original FSAR Volumes;
c. Original SER and Supplements;
d. FSAR Question and Answers;
e. Quality Assurance Plan;
f. Technical Specifications, if not previously provided;
g. Latest IPE/PRA Report; and
h. Vendor Manuals, for applicable systems selected
(2) Assessment and Corrective Actions:
a. The most recent Cyber-Security Quality Assurance (QA) audit and/or
self-assessment; and
b. The last 73.55(m) assessment performed; and
c. Corrective action documents (e.g., condition reports, including status of
corrective actions) generate as a result of the most recent Cyber-Security
Quality Assurance (QA) audit and/or self-assessment.
IV. Information Requested To Be Provided Throughout the Inspection
(1) Copies of any corrective action documents generated as a result of the
inspection teams questions or queries during the inspection.
(2) Copies of the list of questions submitted by the inspection team members and
the status/resolution of the information requested (provided daily during the
inspection to each inspection team member).
If you have any questions regarding the information requested, please contact the inspection
team.