81 FR 9494 - Intent To Request Renewal From OMB of One Current Public Collection of Information: Pipeline Operator Security Information
DEPARTMENT OF HOMELAND SECURITY
Transportation Security Administration Federal Register Volume 81, Issue 37 (February 25, 2016)
Transportation Security Administration
Federal Register Volume 81, Issue 37 (February 25, 2016)
| Page Range | 9494-9495 | |
| FR Document | 2016-04067 |
[Federal Register Volume 81, Number 37 (Thursday, February 25, 2016)] [Notices] [Pages 9494-9495] From the Federal Register Online [www.thefederalregister.org] [FR Doc No: 2016-04067] ----------------------------------------------------------------------- DEPARTMENT OF HOMELAND SECURITY Transportation Security Administration Intent To Request Renewal From OMB of One Current Public Collection of Information: Pipeline Operator Security Information AGENCY: Transportation Security Administration, DHS. ACTION: 60-Day notice. ----------------------------------------------------------------------- SUMMARY: The Transportation Security Administration (TSA) invites public comment on one currently approved Information Collection Request (ICR), Office of Management and Budget (OMB) control number 1652-0055, abstracted below that we will submit to [[Page 9495]] OMB for a revision in compliance with the Paperwork Reduction Act (PRA). The ICR describes the nature of the information collection and its expected burden. Specifically, the collection involves the submission of data concerning pipeline security incidents. DATES: Send your comments by April 25, 2016. ADDRESSES: Comments may be emailed to [email protected] or delivered to the TSA PRA Officer, Office of Information Technology (OIT), TSA-11, Transportation Security Administration, 601 South 12th Street, Arlington, VA 20598-6011. FOR FURTHER INFORMATION CONTACT: Christina A. Walsh at the above address, or by telephone (571) 227-2062. SUPPLEMENTARY INFORMATION: Comments Invited In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 et seq.), an agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid OMB control number. The ICR documentation is available at http://www.reginfo.gov. Therefore, in preparation for OMB review and approval of the following information collection, TSA is soliciting comments to-- (1) Evaluate whether the proposed information requirement is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (2) Evaluate the accuracy of the agency's estimate of the burden; (3) Enhance the quality, utility, and clarity of the information to be collected; and (4) Minimize the burden of the collection of information on those who are to respond, including using appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology. Information Collection Requirement OMB Control Number 1652-0055; Pipeline Operator Security Information. Under the Aviation and Transportation Security Act (ATSA) (Pub. L. 107-71, 115 Stat. 597 (November 19, 2001)) and delegated authority from the Secretary of Homeland Security, TSA has broad responsibility and authority for ``security in all modes of transportation * * * including security responsibilities * * * over modes of transportation that are exercised by the Department of Transportation.'' In executing its responsibility for modal security, TSA produced the Pipeline Security Guidelines in December 2010. As the lead Federal agency for pipeline security, TSA desires to be notified of all incidents which are indicative of a deliberate attempt to disrupt pipeline operations or activities that could be precursors to such an attempt. The Pipeline Security Guidelines encourage pipeline operators to notify the Transportation Security Operations Center (TSOC) via phone at 866-615-5150 or email at [email protected] as soon as possible if any of the following incidents occurs or if there is other reason to believe that a terrorist incident may be planned or may have occurred:Explosions or fires of a suspicious nature affecting pipeline systems, facilities, or assets. Actual or suspected attacks on pipeline systems, facilities, or assets. Bomb threats or weapons of mass destruction (WMD) threats to pipeline systems, facilities, or assets. Theft of pipeline company vehicles, uniforms, or employee credentials. Suspicious persons or vehicles around pipeline systems, facilities, assets, or right-of-way. Suspicious photography or possible surveillance of pipeline systems, facilities, or assets. Suspicious phone calls from people asking about the vulnerabilities or security practices of a pipeline system, facility, or asset operation. Suspicious individuals applying for security-sensitive positions in the pipeline company. Theft or loss of Sensitive Security Information (SSI) (detailed pipeline maps, security plans, etc.). Actual or suspected cyber-attacks that could impact pipeline Supervisory Control and Data Acquisition (SCADA) or enterprise associated IT systems. When contacting the TSOC, the Guidelines request pipeline operators to provide as much of the following information as possible: Name and contact information (email address, telephone number). The time and location of the incident, as specifically as possible. A description of the incident or activity involved. Who has been notified and what actions have been taken. The names and/or descriptions of persons involved or suspicious parties and license plates as appropriate. In addition to the reporting of security incident data to the TSOC, the Pipeline Security Guidelines previously included collecting information on recommendations for the voluntary submission of pipeline operator security manager contact information to TSA. See 74 FR 37723 (July 29, 2009) and 75 FR 49943 (August 16, 2010). TSA is revising the collection of information and will no longer collect the security manager contact information; however, the agency will continue to collect information on the reporting of security incident data to TSOC. TSA expects reporting of pipeline security incidents will occur on an irregular basis. TSA estimates that approximately 30 incidents will be reported annually, requiring a maximum of 30 minutes to collect, review, and submit event information. The potential burden to the public is estimated to be 15 hours (30 incidents x 30 minutes = 15 hours). Dated: February 22, 2016. Christina A. Walsh, TSA Paperwork Reduction Act Officer, Office of Information Technology. [FR Doc. 2016-04067 Filed 2-24-16; 8:45 am] BILLING CODE 9110-05-P
![9494 Federal Register / Vol. 81, No. 37 / Thursday, February 25, 2016 / Notices
(RDP), First Responder Group (FRG), of the public will register at the to three minutes per speaker, with no
Capability Development Support (CDS) registration table prior to entering the more than 15 minutes for all speakers.
and Homeland Security Advanced meeting room. For information on Parties interested in making in-person
Research Projects Agency (HSARPA). facilities or services for individuals with comments should register on the Public
The rest of the afternoon will consist of disabilities, or to request special Comment Registration list available at
breakout sessions for discussion on the assistance at the meeting, contact the the entrance to the meeting location
issues presented earlier by S&T person listed under FOR FURTHER prior to the beginning of the meeting.
leadership. This session will be INFORMATION CONTACT below as soon as FOR FURTHER INFORMATION CONTACT:
followed by questions and comments possible. Ginger Norris, National Infrastructure
from the public. Day 2: The morning To facilitate public participation, we Advisory Council, Alternate Designated
session will begin with a small working are inviting public comment on the Federal Officer, Department of
group session focused on developing issues to be considered by the Council Homeland Security, (703) 235–2888.
whitepapers, implementation plans, and as listed in the SUMMARY section below. SUPPLEMENTARY INFORMATION: Notice of
tangible recommendations from the Comments must be submitted in writing this meeting is given under the Federal
HSSTAC. The afternoon session will no later than 12:00 p.m. on March Advisory Committee Act, 5 U.S.C.
include a continuation of the breakout 9,2016, in order to be considered by the Appendix. The National Infrastructure
session, followed by a presentation of an Council in its meeting. The comments Advisory Council shall provide the
executive summary of the group’s must be identified by ‘‘DHS–2016– President, through the Secretary of
discussions. This session will be 0005,’’ and may be submitted by any Homeland Security, with advice on the
followed by questions and comments one of the following methods: security and resilience of the Nation’s
from the public. The committee will • Federal eRulemaking Portal: critical infrastructure sectors. The NIAC
then deliberate on any preliminary www.regulations.gov. Follow the will meet to discuss issues relevant to
recommendations, and formulate initial instructions for submitting written critical infrastructure security and
recommendations on the science and comments. resilience as directed by the President.
technology issues presented earlier. • Email: NIAC@hq.dhs.gov. Include The meeting will commence at 1:30
the docket number in the subject line of p.m. EST. At this meeting, the council
Dated: February 22, 2016. the message. will discuss its on-going study on Water
Bishop Garrison, • Fax: (703) 235–9707.
Executive Director, Homeland Security • Mail: Ginger Norris, National Resilience. All presentations will be
Science and Technology Advisory Committee. Protection and Programs Directorate, posted prior to the meeting on the
[FR Doc. 2016–04068 Filed 2–24–16; 8:45 am] Department of Homeland Security, 245 Council’s public Web page—
BILLING CODE 9110–9F–P Murray Lane SW., Mail Stop 0612, www.dhs.gov/NIAC.
Washington, DC 20598–0607. Public Meeting Agenda
Instructions: All written submissions
DEPARTMENT OF HOMELAND I. Opening of Meeting
received must include the words II. Roll Call of Members
SECURITY ‘‘Department of Homeland Security’’ III. Opening Remarks and Introductions
[Docket No. DHS–2016–0005] and the docket number for this action. IV. Approval of Meeting Minutes
Written comments received will be V. Status Update on Water Resilience
National Infrastructure Advisory posted without alteration at Working Group
Council www.regulations.gov, including any VI. Open Discussion and Public Comment
personal information provided. VII. Closing Remarks
AGENCY: National Protection and Docket: For access to the docket or to Dated: February 19, 2016.
Programs Directorate, DHS. read background documents or Ginger Norris,
ACTION: Committee Management; Notice comments received by the National Alternate Designated Federal Officer for the
of an Open Federal Advisory Committee Infrastructure Advisory Council, go to National Infrastructure Advisory Council.
Meeting. www.regulations.gov. Enter ‘‘NIAC’’ in [FR Doc. 2016–03925 Filed 2–24–16; 8:45 am]
the search line and the Web site will list
SUMMARY: The National Infrastructure BILLING CODE 9110–9B–P
all relevant documents for your review.
Advisory Council will meet Monday, Members of the public will have an
March 14, 2016, at 1310 N. Courthouse opportunity to provide oral comments
Road, Suite 300, the Virginia Conference DEPARTMENT OF HOMELAND
on the topics on the meeting agenda SECURITY
Room, Arlington, VA 22201. This below, and on any previous studies
meeting will be open to the public. issued by the National Infrastructure Transportation Security Administration
DATES: The National Infrastructure Advisory Council. We request that
Advisory Council will meet on March comments be limited to the issues and Intent To Request Renewal From OMB
14, 2015 from 1:30 p.m.–3:30 p.m. EST. studies listed in the meeting agenda and of One Current Public Collection of
The meeting may close early if the previous National Infrastructure Information: Pipeline Operator Security
committee has completed its business. Advisory Council studies. All previous Information
For additional information, please National Infrastructure Advisory
consult the National Infrastructure AGENCY: Transportation Security
Council studies can be located at Administration, DHS.
Advisory Council Web site, www.dhs.gov/NIAC. Public comments
www.dhs.gov/NIAC, or contact the ACTION: 60-Day notice.
mstockstill on DSK4VPTVN1PROD with NOTICES
may be submitted in writing or
National Infrastructure Advisory presented in person for the Council to SUMMARY: The Transportation Security
Council Secretariat by phone at (703) consider. Comments received by Ginger Administration (TSA) invites public
235–2888 or by email at NIAC@ Norris on or after 1:30 p.m. on March comment on one currently approved
hq.dhs.gov. 14, 2015, will still be accepted and Information Collection Request (ICR),
ADDRESSES: 1310 N. Courthouse Road, reviewed by the members, but not Office of Management and Budget
Suite 300, the Virginia Conference necessarily at the time of the meeting. (OMB) control number 1652–0055,
Room, Arlington, VA 22201. Members In-person presentations will be limited abstracted below that we will submit to
VerDate Sep<11>2014 18:07 Feb 24, 2016 Jkt 238001 PO 00000 Frm 00076 Fmt 4703 Sfmt 4703 E:\FR\FM\25FEN1.SGM 25FEN1](https://thefederalregister.org/doc/81_FR_9531/page/1.svg)
![Federal Register / Vol. 81, No. 37 / Thursday, February 25, 2016 / Notices 9495
OMB for a revision in compliance with security, TSA produced the Pipeline manager contact information to TSA.
the Paperwork Reduction Act (PRA). Security Guidelines in December 2010. See 74 FR 37723 (July 29, 2009) and 75
The ICR describes the nature of the As the lead Federal agency for FR 49943 (August 16, 2010). TSA is
information collection and its expected pipeline security, TSA desires to be revising the collection of information
burden. Specifically, the collection notified of all incidents which are and will no longer collect the security
involves the submission of data indicative of a deliberate attempt to manager contact information; however,
concerning pipeline security incidents. disrupt pipeline operations or activities the agency will continue to collect
DATES: Send your comments by April that could be precursors to such an information on the reporting of security
25, 2016. attempt. The Pipeline Security incident data to TSOC.
Guidelines encourage pipeline operators TSA expects reporting of pipeline
ADDRESSES: Comments may be emailed
to notify the Transportation Security security incidents will occur on an
to TSAPRA@dhs.gov or delivered to the Operations Center (TSOC) via phone at irregular basis. TSA estimates that
TSA PRA Officer, Office of Information 866–615–5150 or email at TSOC.ST@ approximately 30 incidents will be
Technology (OIT), TSA–11, dhs.gov as soon as possible if any of the reported annually, requiring a
Transportation Security Administration, following incidents occurs or if there is maximum of 30 minutes to collect,
601 South 12th Street, Arlington, VA other reason to believe that a terrorist review, and submit event information.
20598–6011. incident may be planned or may have The potential burden to the public is
FOR FURTHER INFORMATION CONTACT: occurred: estimated to be 15 hours (30 incidents
Christina A. Walsh at the above address, • Explosions or fires of a suspicious × 30 minutes = 15 hours).
or by telephone (571) 227–2062. nature affecting pipeline systems, Dated: February 22, 2016.
SUPPLEMENTARY INFORMATION: facilities, or assets. Christina A. Walsh,
• Actual or suspected attacks on
Comments Invited TSA Paperwork Reduction Act Officer, Office
pipeline systems, facilities, or assets.
of Information Technology.
In accordance with the Paperwork • Bomb threats or weapons of mass
[FR Doc. 2016–04067 Filed 2–24–16; 8:45 am]
Reduction Act of 1995 (44 U.S.C. 3501 destruction (WMD) threats to pipeline
systems, facilities, or assets. BILLING CODE 9110–05–P
et seq.), an agency may not conduct or
sponsor, and a person is not required to • Theft of pipeline company vehicles,
respond to, a collection of information uniforms, or employee credentials.
unless it displays a valid OMB control • Suspicious persons or vehicles DEPARTMENT OF THE INTERIOR
number. The ICR documentation is around pipeline systems, facilities,
assets, or right-of-way. Fish and Wildlife Service
available at http://www.reginfo.gov.
Therefore, in preparation for OMB • Suspicious photography or possible [FWS–R8–ES–2016–N028;
review and approval of the following surveillance of pipeline systems, FXES11130800000–167–FF08E00000]
information collection, TSA is soliciting facilities, or assets.
comments to— • Suspicious phone calls from people Endangered Species Recovery Permit
asking about the vulnerabilities or Applications
(1) Evaluate whether the proposed
security practices of a pipeline system,
information requirement is necessary for AGENCY: Fish and Wildlife Service,
facility, or asset operation.
the proper performance of the functions Interior.
• Suspicious individuals applying for
of the agency, including whether the ACTION: Notice of receipt of permit
security-sensitive positions in the
information will have practical utility; applications; request for comment.
pipeline company.
(2) Evaluate the accuracy of the • Theft or loss of Sensitive Security
agency’s estimate of the burden; SUMMARY: We, the U.S. Fish and
Information (SSI) (detailed pipeline Wildlife Service, invite the public to
(3) Enhance the quality, utility, and maps, security plans, etc.).
clarity of the information to be comment on the following applications
• Actual or suspected cyber-attacks to conduct certain activities with
collected; and that could impact pipeline Supervisory
(4) Minimize the burden of the endangered species. With some
Control and Data Acquisition (SCADA) exceptions, the Endangered Species Act
collection of information on those who or enterprise associated IT systems.
are to respond, including using (Act) prohibits activities with
When contacting the TSOC, the endangered and threatened species
appropriate automated, electronic, Guidelines request pipeline operators to
mechanical, or other technological unless a Federal permit allows such
provide as much of the following activity. The Act also requires that we
collection techniques or other forms of information as possible: invite public comment before issuing
information technology. • Name and contact information recovery permits to conduct certain
Information Collection Requirement (email address, telephone number). activities with endangered species.
• The time and location of the
OMB Control Number 1652–0055; DATES: Comments on these permit
incident, as specifically as possible.
Pipeline Operator Security Information. • A description of the incident or applications must be received on or
Under the Aviation and Transportation activity involved. before March 28, 2016.
Security Act (ATSA) (Pub. L. 107–71, • Who has been notified and what ADDRESSES: Written data or comments
115 Stat. 597 (November 19, 2001)) and actions have been taken. should be submitted to the Endangered
delegated authority from the Secretary • The names and/or descriptions of Species Program Manager, U.S. Fish and
Wildlife Service, Region 8, 2800 Cottage
mstockstill on DSK4VPTVN1PROD with NOTICES
of Homeland Security, TSA has broad persons involved or suspicious parties
responsibility and authority for and license plates as appropriate. Way, Room W–2606, Sacramento, CA
‘‘security in all modes of transportation In addition to the reporting of security 95825 (telephone: 916–414–6464; fax:
* * * including security incident data to the TSOC, the Pipeline 916–414–6486). Please refer to the
responsibilities * * * over modes of Security Guidelines previously included respective permit number for each
transportation that are exercised by the collecting information on application when submitting comments.
Department of Transportation.’’ In recommendations for the voluntary FOR FURTHER INFORMATION CONTACT:
executing its responsibility for modal submission of pipeline operator security Daniel Marquez, Fish and Wildlife
VerDate Sep<11>2014 18:07 Feb 24, 2016 Jkt 238001 PO 00000 Frm 00077 Fmt 4703 Sfmt 4703 E:\FR\FM\25FEN1.SGM 25FEN1](https://thefederalregister.org/doc/81_FR_9531/page/2.svg)
Document Created: 2018-02-02 14:35:20
Document Modified: 2018-02-02 14:35:20
| Category | Regulatory Information | |
| Collection | Federal Register | |
| sudoc Class | AE 2.7: GS 4.107: AE 2.106: | |
| Publisher | Office of the Federal Register, National Archives and Records Administration | |
| Section | Notices | |
| Action | 60-Day notice. | |
| Dates | Send your comments by April 25, 2016. | |
| Contact | Christina A. Walsh at the above | |
| FR Citation | 81 FR 9494 |
2025 Federal Register | Disclaimer | Privacy Policy
USC | CFR | eCFR