Intent To Request Extension From OMB of One Current Public Collection of Information: Pipeline Operator Security Information, 54368-54369 [2018-23593]

Download as PDF 54368 Federal Register / Vol. 83, No. 209 / Monday, October 29, 2018 / Notices ASAC members and non-TSA staff must register in advance with their full name and date of birth to attend. Due to space constraints, the meeting is limited to 75 people, including ASAC members and staff, on a first to register basis. Attendees are required to present government-issued photo identification to verify identity. In addition, members of the public must make advance arrangements, as stated below, to present oral or written statements specifically addressing issues pertaining to the items listed in the Meeting Agenda section below. The public comment period will begin at approximately 11 a.m., depending on the meeting progress. Speakers are requested to limit their comments to three minutes. Contact the person listed in the FOR FURTHER INFORMATION CONTACT section no later than November 23, 2018, to register to attend the meeting and/or to present oral or written statements addressing issues pertaining to the items listed in the Meeting Agenda section below. Anyone in need of assistance or a reasonable accommodation for the meeting should contact the person listed in the FOR FURTHER INFORMATION CONTACT section. Meeting Agenda amozie on DSK3GDR082PROD with NOTICES1 The Committee will meet to discuss items listed in the agenda below: • Legislative Update • Subcommittee and Work Group briefings on calendar year (CY) 2018 activities, key issues, and areas of focus for CY 2019: Æ Air Cargo Æ Airport Æ General Aviation Æ Insider Threat Æ International Aviation Æ Security Technology Æ Secondary Barriers Working Group • Public Comments • Discussion of the CY 2019 Committee Agenda • Closing Comments and Adjournment Dated: October 19, 2018. Eddie D. Mayenschein, Assistant Administrator, Office of Security Policy and Industry Engagement. [FR Doc. 2018–23595 Filed 10–26–18; 8:45 am] BILLING CODE 9110–05–P VerDate Sep<11>2014 17:48 Oct 26, 2018 Jkt 247001 SUMMARY: 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. 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 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 DEPARTMENT OF HOMELAND SECURITY Transportation Security Administration Intent To Request Extension From OMB of One Current Public Collection of Information: Pipeline Operator Security Information Transportation Security Administration, DHS. ACTION: 60-Day notice. AGENCY: 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: PO 00000 Frm 00061 Fmt 4703 Sfmt 4703 E:\FR\FM\29OCN1.SGM 29OCN1 Federal Register / Vol. 83, No. 209 / Monday, October 29, 2018 / Notices 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] BILLING CODE 9110–05–P DEPARTMENT OF HOMELAND SECURITY Transportation Security Administration [Docket No. TSA–2002–11602] Extension of Agency Information Collection Activity Under OMB Review: Security Programs for Foreign Air Carriers Transportation Security Administration, DHS. ACTION: 30-Day notice. AGENCY: This notice announces that the Transportation Security Administration (TSA) has forwarded the Information Collection Request (ICR), Office of Management and Budget (OMB) control number 1652–0005, abstracted below to OMB for review and approval of an extension of the currently approved collection under the Paperwork Reduction Act (PRA). The amozie on DSK3GDR082PROD with NOTICES1 SUMMARY: VerDate Sep<11>2014 17:48 Oct 26, 2018 Jkt 247001 ICR describes the nature of the information collection and its expected burden. This information collection is mandatory for foreign air carriers and must be submitted prior to entry into the United States. DATES: Send your comments by November 28, 2018. A comment to OMB is most effective if OMB receives it within 30 days of publication. ADDRESSES: Interested persons are invited to submit written comments on the proposed information collection to the Office of Information and Regulatory Affairs, OMB. Comments should be addressed to Desk Officer, Department of Homeland Security/TSA, and sent via electronic mail to dhsdeskofficer@ omb.eop.gov. FOR FURTHER INFORMATION CONTACT: Christina A. Walsh, TSA PRA Officer, Information Technology (IT), TSA–11, Transportation Security Administration, 601 South 12th Street, Arlington, VA 20598–6011; telephone (571) 227–2062; email TSAPRA@dhs.gov. SUPPLEMENTARY INFORMATION: TSA published a Federal Register notice, with a 60-day comment period soliciting comments, of the following collection of information on June 19, 2018, 83 FR 28444. 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 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 PO 00000 Frm 00062 Fmt 4703 Sfmt 9990 54369 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 Title: Security Programs for Foreign Air Carriers. Type of Request: Extension of a currently approved collection. OMB Control Number: 1652–0005. Forms(s): N/A. Affected Public: Foreign air carriers. Abstract: TSA uses the information collected to determine compliance with 49 CFR part 1546 and to ensure passenger safety by monitoring foreign air carrier security procedures. Foreign air carriers must carry out security measures to provide for the safety of persons and property traveling on flights provided by the foreign air carrier against acts of criminal violence and air piracy, and the introduction of explosives, incendiaries, or weapons aboard an aircraft. The foreign air carrier’s security program must provide a level of protection similar to the level of protection provided by U.S. aircraft operators serving the same airports, and the foreign air carrier must employ procedures equivalent to those required of U.S. aircraft operators serving the same airport, if TSA determines such procedures are necessary to provide a similar level of protection. This information collection is mandatory for foreign air carriers and must be submitted prior to entry into the United States. The TSA information collection includes providing information to TSA as set forth in the carrier’s security program, which includes any amendments; maintaining records of compliance with 49 CFR part 1546 and the foreign air carrier’s security program, including security training records; suspicious incident reporting; and submitting identifying information on foreign air carriers’ flight crews and passengers. Number of Respondents: 180. Estimated Annual Burden Hours: An estimated 1,278,352 hours annually. Dated: October 23, 2018. Christina A. Walsh, TSA Paperwork Reduction Act Officer, Information Technology. [FR Doc. 2018–23594 Filed 10–26–18; 8:45 am] BILLING CODE 9110–05–P E:\FR\FM\29OCN1.SGM 29OCN1

Agencies

[Federal Register Volume 83, Number 209 (Monday, October 29, 2018)]
[Notices]
[Pages 54368-54369]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2018-23593]


-----------------------------------------------------------------------

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 [email protected] 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

[[Page 54369]]

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]
 BILLING CODE 9110-05-P