Intent To Request Extension From OMB of One Current Public Collection of Information: Pipeline Operator Security Information, 90305-90306 [2024-26538]

Download as PDF Federal Register / Vol. 89, No. 221 / Friday, November 15, 2024 / Notices prelimdownload and the respective Community Map Repository address listed in the tables. For communities with multiple ongoing Preliminary studies, the studies can be identified by the unique project number and Preliminary FIRM date listed in the tables. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at https://msc.fema.gov for comparison. Community 90305 (Catalog of Federal Domestic Assistance No. 97.022, ‘‘Flood Insurance.’’) Nicholas A. Shufro, Assistant Administrator (Acting) for Risk Management, Federal Emergency Management Agency, Department of Homeland Security. Community map repository address Hampshire County, West Virginia and Incorporated Areas Project: 21–03–0004S Preliminary Date: February 23, 2024 Unincorporated Areas of Hampshire County ........................................... Town of Capon Bridge ............................................................................. Town of Romney ...................................................................................... [FR Doc. 2024–26673 Filed 11–14–24; 8:45 am] BILLING CODE 9110–12–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 Transportation Security Administration, Department of Homeland Security. AGENCY: ACTION: 60-Day notice. 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 collection of pipeline security incident data, and the cybersecurity coordinator(s) and alternate(s) contact information. SUMMARY: Send your comments by January 14, 2025. DATES: Comments may be emailed to TSAPRA@tsa.dhs.gov or delivered to the TSA PRA Officer, Information Technology (IT), TSA–11, Transportation Security Administration, 6595 Springfield Center Drive, Springfield, VA 20598–6011. khammond on DSKJM1Z7X2PROD with NOTICES ADDRESSES: FOR FURTHER INFORMATION CONTACT: Christina A. Walsh at the above address, or by telephone (571) 227–2062. SUPPLEMENTARY INFORMATION: VerDate Sep<11>2014 16:11 Nov 14, 2024 Jkt 265001 Hampshire County Courthouse, 19 East Main Street, Romney, WV 26757. Hampshire County Courthouse, 19 East Main Street, Romney, WV 26757. Town Hall, 340 East Main Street, Romney, WV 26757. 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 https://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. 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, PO 00000 Frm 00046 Fmt 4703 Sfmt 4703 TSA produced Pipeline Security Guidelines in December 2010 and 2011, with an update published in April 2021. These voluntary guidelines were developed with the assistance of industry and government members of the Pipeline Sector and Government Coordinating Councils, industry association representatives, and other interested parties. Voluntary Collection. 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 via phone or email as soon as possible if incidents occur or if there is other reason to believe that a terrorist incident may be planned or may have occurred. When voluntarily contacting the Transportation Security Operations Center, the Guidelines request pipeline operators to provide as much information about the incident as possible. Mandatory Collection. In May 2021, TSA issued a Security Directive (SD) series with requirements for owner/ operators of hazardous liquid and natural gas pipelines and liquefied natural gas facilities that TSA designated as critical. The SD series included two mandatory information collections: 1. TSA requires all owner/operators subject to the SD’s requirements to report actual or potential cybersecurity incidents affecting their information technology and operational technology systems to the Cybersecurity and Infrastructure Security Agency (CISA) within 24 hours of discovery, using the CISA Incident Reporting System. E:\FR\FM\15NON1.SGM 15NON1 90306 Federal Register / Vol. 89, No. 221 / Friday, November 15, 2024 / Notices 2. The SD series requires critical pipeline owner/operators to appoint cybersecurity coordinator(s) or alternate(s) at the corporate level and to provide contact information for the coordinators to TSA. To ensure that information reported pursuant to the SD series is identifiable within the system, TSA requires these owners/operators to indicate that they are providing the information pursuant to the SD series. TSA expects voluntary reporting of pipeline security incidents will occur on an irregular basis. TSA estimates that pipeline owner/operators will report approximately 118 incidents annually, requiring an average of 30 minutes (0.50 hour) to collect, review, and submit event information. The total potential burden to the public for this task is estimated to be 59 hours. Using the CISA Incident Reporting System, TSA expects the mandatory reporting of pipeline cybersecurity incidents to CISA will occur 20 times per year for each covered pipeline owner/operator. TSA estimates that 100 pipeline owner/operators will take approximately 2 hours to gather the appropriate information to submit each incident report. The potential burden to the public for this task is 20 × 100 × 2 hours = 4,000 hours. TSA estimates that approximately 100 pipeline owner/operators will report their cybersecurity manager and alternate point of contact information. It will take the pipeline owner/operator approximately 30 minutes (0.50 hour) to do so, and the potential burden for this task is 100 × 0.50 hour = 50 hours. Therefore, the total hour burden to the public for this information collection request is estimated to be 59 hours (Security Incidents) + 4,000 hours (CISA Reporting) + 50 hours (Cyber POC) = 4,109 hours annually. Dated: November 8, 2024. Christina A. Walsh, TSA Paperwork Reduction Act Officer, Information Technology. [FR Doc. 2024–26538 Filed 11–14–24; 8:45 am] BILLING CODE 9110–05–P DEPARTMENT OF THE INTERIOR Fish and Wildlife Service khammond on DSKJM1Z7X2PROD with NOTICES [Docket No. FWS–R7–NWRS–2023–0072; FF07R00000–245–FXRS12610700000] Notice of Availability; Draft Supplemental Environmental Impact Statement for a Potential Land Exchange Involving Izembek National Wildlife Refuge Lands; Public Meetings AGENCY: Fish and Wildlife Service, Interior. VerDate Sep<11>2014 16:11 Nov 14, 2024 Jkt 265001 ACTION: Notice of availability. In accordance with the National Environmental Policy Act of 1969, as amended, and the Alaska National Interest Lands Conservation Act of 1980, as amended, along with other laws as applicable, we, the U.S. Fish and Wildlife Service (FWS), announce the availability of a draft supplemental environmental impact statement (draft supplemental EIS) to consider the effects of a potential land exchange of certain lands owned by the King Cove Corporation with certain lands owned by the U.S. Government and located within the Izembek National Wildlife Refuge and Izembek Wilderness Area. If a land exchange is approved, King Cove Corporation would use the acquired land for a road corridor for noncommercial use. We invite comment on the draft supplemental EIS from the public and local, State, Tribal, and Federal agencies. We will separately be announcing public meetings. SUMMARY: DATES: Submitting Comments: We must receive your written comments on or before December 30, 2024. Comments submitted online at https:// www.regulations.gov/ must be received by 11:59 p.m. eastern time on December 30, 2024. Public Meetings: Meeting locations, dates, and times will be announced at https://www.fws.gov/project/potentialland-exchange-road-between-king-coveand-cold-bay. ADDRESSES: Obtaining Documents: The draft supplemental EIS, as well as any comments and other materials that we receive, will be available for public inspection online in Docket No. FWS– R7–NWRS–2023–0072 at https:// www.regulations.gov. In addition, to inform public comment, we are also making FWS’s 2013 EIS and record of decision (ROD) documents available for review at https://www.regulations.gov in Docket No. FWS–R7–NWRS–2023– 0072. However, we are not taking public comments on those documents at this time. Submitting Public Comments: You may submit comments by any of the following methods: • Online: https:// www.regulations.gov. Follow the instructions for submitting comments on Docket No. FWS–R7–NWRS–2023– 0072. • U.S. Mail: Public Comments Processing, Attn: Docket No. FWS–R7– NWRS–2023–0072; U.S. Fish and Wildlife Service, MS: PRB/3W; 5275 PO 00000 Frm 00047 Fmt 4703 Sfmt 4703 Leesburg Pike; Falls Church, VA 22041– 3803. • Public Meetings and any Subsistence Hearings: Comments will also be accepted at the in-person and virtual public meetings/hearings. Meeting locations, dates, and times will be announced at https://www.fws.gov/ project/potential-land-exchange-roadbetween-king-cove-and-cold-bay. We will post all written comments on https://www.regulations.gov. This generally means that we will post any personal information you provide us (see Public Review Process for more information). Reasonable Accommodations for Meetings: Persons needing reasonable accommodations to attend and participate in the public meetings should contact Bobbie Jo Skibo as soon as possible (see FOR FURTHER INFORMATION CONTACT). To allow sufficient time to process requests, please make contact no later than 1 week before the desired public meeting. Information and documents are available in alternative formats upon request. FOR FURTHER INFORMATION CONTACT: Bobbie Jo Skibo, Project Leader, by telephone at 907–441–1539; by email at bobbiejo_skibo@fws.gov; or by U.S. mail at U.S. Fish and Wildlife Service, Alaska Region, National Wildlife Refuge System, 1011 East Tudor Road, Anchorage, AK 99503. Contact Bobbie Jo Skibo to have your name added to our mailing list. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-ofcontact in the United States. SUPPLEMENTARY INFORMATION: Introduction In accordance with the National Environmental Policy Act of 1969, as amended (NEPA; 42 U.S.C. 4321 et seq.), and the Alaska National Interest Lands Conservation Act of 1980, as amended (ANILCA; Pub. L. 96–487, sec. 1302(h), Dec. 2, 1980; 16 U.S.C. 3192(h)), along with other laws as applicable, we, the U.S. Fish and Wildlife Service (FWS), announce the availability of a draft supplemental environmental impact statement (draft supplemental EIS) to consider the effects of a potential land exchange of certain lands owned by the King Cove Corporation with certain lands that are owned by the U.S. Government and E:\FR\FM\15NON1.SGM 15NON1

Agencies

[Federal Register Volume 89, Number 221 (Friday, November 15, 2024)]
[Notices]
[Pages 90305-90306]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2024-26538]


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

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, Department of Homeland 
Security.

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 collection of pipeline 
security incident data, and the cybersecurity coordinator(s) and 
alternate(s) contact information.

DATES: Send your comments by January 14, 2025.

ADDRESSES: Comments may be emailed to [email protected] or delivered 
to the TSA PRA Officer, Information Technology (IT), TSA-11, 
Transportation Security Administration, 6595 Springfield Center Drive, 
Springfield, 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 https://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.

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 and 2011, with an update published in April 
2021. These voluntary guidelines were developed with the assistance of 
industry and government members of the Pipeline Sector and Government 
Coordinating Councils, industry association representatives, and other 
interested parties.
    Voluntary Collection. 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 via 
phone or email as soon as possible if incidents occur or if there is 
other reason to believe that a terrorist incident may be planned or may 
have occurred. When voluntarily contacting the Transportation Security 
Operations Center, the Guidelines request pipeline operators to provide 
as much information about the incident as possible.
    Mandatory Collection. In May 2021, TSA issued a Security Directive 
(SD) series with requirements for owner/operators of hazardous liquid 
and natural gas pipelines and liquefied natural gas facilities that TSA 
designated as critical. The SD series included two mandatory 
information collections:
    1. TSA requires all owner/operators subject to the SD's 
requirements to report actual or potential cybersecurity incidents 
affecting their information technology and operational technology 
systems to the Cybersecurity and Infrastructure Security Agency (CISA) 
within 24 hours of discovery, using the CISA Incident Reporting System.

[[Page 90306]]

    2. The SD series requires critical pipeline owner/operators to 
appoint cybersecurity coordinator(s) or alternate(s) at the corporate 
level and to provide contact information for the coordinators to TSA. 
To ensure that information reported pursuant to the SD series is 
identifiable within the system, TSA requires these owners/operators to 
indicate that they are providing the information pursuant to the SD 
series.
    TSA expects voluntary reporting of pipeline security incidents will 
occur on an irregular basis. TSA estimates that pipeline owner/
operators will report approximately 118 incidents annually, requiring 
an average of 30 minutes (0.50 hour) to collect, review, and submit 
event information. The total potential burden to the public for this 
task is estimated to be 59 hours.
    Using the CISA Incident Reporting System, TSA expects the mandatory 
reporting of pipeline cybersecurity incidents to CISA will occur 20 
times per year for each covered pipeline owner/operator. TSA estimates 
that 100 pipeline owner/operators will take approximately 2 hours to 
gather the appropriate information to submit each incident report. The 
potential burden to the public for this task is 20 x 100 x 2 hours = 
4,000 hours.
    TSA estimates that approximately 100 pipeline owner/operators will 
report their cybersecurity manager and alternate point of contact 
information. It will take the pipeline owner/operator approximately 30 
minutes (0.50 hour) to do so, and the potential burden for this task is 
100 x 0.50 hour = 50 hours.
    Therefore, the total hour burden to the public for this information 
collection request is estimated to be 59 hours (Security Incidents) + 
4,000 hours (CISA Reporting) + 50 hours (Cyber POC) = 4,109 hours 
annually.

    Dated: November 8, 2024.
Christina A. Walsh,
TSA Paperwork Reduction Act Officer, Information Technology.
[FR Doc. 2024-26538 Filed 11-14-24; 8:45 am]
BILLING CODE 9110-05-P


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.