Notices. 60-Day notice
848 words·~4 min read·
/register/2018/10/29/2018-23593A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
BILLING CODE 9110-05-P DEPARTMENT OF HOMELAND SECURITY Transportation Security Administration Intent To Request Extension 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 OMB for an extension 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 December 28, 2018. ADDRESSES: Comments may be emailed to *TSAPRA@tsa.dhs.gov* or delivered to the TSA PRA Officer, Information Technology (IT), 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 will be available at *http://www.reginfo.gov* upon its submission to OMB. 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. Consistent with the requirements of Executive Order (E.O.) 13771, Reducing Regulation and Controlling Regulatory Costs, and E.O. 13777, Enforcing the Regulatory Reform Agenda, TSA is also requesting comments on the extent to which this request for information could be modified to reduce the burden on respondents. Information Collection Requirement *OMB Control Number 1652-0055; Pipeline Operator Security Information.* In addition to TSA's broad responsibility and authority for “security in all modes of transportation . . . including security responsibilities . . . over modes of transportation[,]” *see* 49 U.S.C. 114, TSA is required to issue recommendations for pipeline security measures and conduct inspections to assess implementation of the recommendations. *See* sec. 1557 of the Implementing Recommendations of the 9/11 Commission Act of 2007, Public Law 110-53 (August 3, 2007). Consistent with these requirements, TSA produced Pipeline Security Guidelines in December 2010, with an update published in March 2018. As the lead Federal agency for pipeline security and consistent with its statutory authorities, TSA needs to be notified of all
(1)incidents that may indicate a deliberate attempt to disrupt pipeline operations and
(2)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 or email 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 voluntarily 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. TSA expects voluntary reporting of pipeline security incidents will occur on an irregular basis. TSA estimates that approximately 32 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 16 hours. Dated: October 23, 2018. Christina A. Walsh, TSA Paperwork Reduction Act Officer, Information Technology. [FR Doc. 2018-23593 Filed 10-26-18; 8:45 am]
Connectionstraces to 2
Traces to 2 documents
1 reference not yet in our index
- Pub. L. 110-53
Citation graph
cites case law
Cites 3Cited by 0 across 0 sources