Intent To Request Renewal From OMB of One Current Public Collection of Information: Pipeline Operator Security Information, 9494-9495 [2016-04067]
Download as PDF
<![CDATA[
9494
Federal Register / Vol. 81, No. 37 / Thursday, February 25, 2016 / Notices
(RDP), First Responder Group (FRG),
Capability Development Support (CDS)
and Homeland Security Advanced
Research Projects Agency (HSARPA).
The rest of the afternoon will consist of
breakout sessions for discussion on the
issues presented earlier by S&T
leadership. This session will be
followed by questions and comments
from the public. Day 2: The morning
session will begin with a small working
group session focused on developing
whitepapers, implementation plans, and
tangible recommendations from the
HSSTAC. The afternoon session will
include a continuation of the breakout
session, followed by a presentation of an
executive summary of the group’s
discussions. This session will be
followed by questions and comments
from the public. The committee will
then deliberate on any preliminary
recommendations, and formulate initial
recommendations on the science and
technology issues presented earlier.
Dated: February 22, 2016.
Bishop Garrison,
Executive Director, Homeland Security
Science and Technology Advisory Committee.
[FR Doc. 2016–04068 Filed 2–24–16; 8:45 am]
BILLING CODE 9110–9F–P
DEPARTMENT OF HOMELAND
SECURITY
[Docket No. DHS–2016–0005]
National Infrastructure Advisory
Council
National Protection and
Programs Directorate, DHS.
ACTION: Committee Management; Notice
of an Open Federal Advisory Committee
Meeting.
AGENCY:
The National Infrastructure
Advisory Council will meet Monday,
March 14, 2016, at 1310 N. Courthouse
Road, Suite 300, the Virginia Conference
Room, Arlington, VA 22201. This
meeting will be open to the public.
DATES: The National Infrastructure
Advisory Council will meet on March
14, 2015 from 1:30 p.m.–3:30 p.m. EST.
The meeting may close early if the
committee has completed its business.
For additional information, please
consult the National Infrastructure
Advisory Council Web site,
www.dhs.gov/NIAC, or contact the
National Infrastructure Advisory
Council Secretariat by phone at (703)
235–2888 or by email at NIAC@
hq.dhs.gov.
ADDRESSES: 1310 N. Courthouse Road,
Suite 300, the Virginia Conference
Room, Arlington, VA 22201. Members
mstockstill on DSK4VPTVN1PROD with NOTICES
SUMMARY:
VerDate Sep<11>2014
18:07 Feb 24, 2016
Jkt 238001
of the public will register at the
registration table prior to entering the
meeting room. For information on
facilities or services for individuals with
disabilities, or to request special
assistance at the meeting, contact the
person listed under FOR FURTHER
INFORMATION CONTACT below as soon as
possible.
To facilitate public participation, we
are inviting public comment on the
issues to be considered by the Council
as listed in the SUMMARY section below.
Comments must be submitted in writing
no later than 12:00 p.m. on March
9,2016, in order to be considered by the
Council in its meeting. The comments
must be identified by ‘‘DHS–2016–
0005,’’ and may be submitted by any
one of the following methods:
• Federal eRulemaking Portal:
www.regulations.gov. Follow the
instructions for submitting written
comments.
• Email: NIAC@hq.dhs.gov. Include
the docket number in the subject line of
the message.
• Fax: (703) 235–9707.
• Mail: Ginger Norris, National
Protection and Programs Directorate,
Department of Homeland Security, 245
Murray Lane SW., Mail Stop 0612,
Washington, DC 20598–0607.
Instructions: All written submissions
received must include the words
‘‘Department of Homeland Security’’
and the docket number for this action.
Written comments received will be
posted without alteration at
www.regulations.gov, including any
personal information provided.
Docket: For access to the docket or to
read background documents or
comments received by the National
Infrastructure Advisory Council, go to
www.regulations.gov. Enter ‘‘NIAC’’ in
the search line and the Web site will list
all relevant documents for your review.
Members of the public will have an
opportunity to provide oral comments
on the topics on the meeting agenda
below, and on any previous studies
issued by the National Infrastructure
Advisory Council. We request that
comments be limited to the issues and
studies listed in the meeting agenda and
previous National Infrastructure
Advisory Council studies. All previous
National Infrastructure Advisory
Council studies can be located at
www.dhs.gov/NIAC. Public comments
may be submitted in writing or
presented in person for the Council to
consider. Comments received by Ginger
Norris on or after 1:30 p.m. on March
14, 2015, will still be accepted and
reviewed by the members, but not
necessarily at the time of the meeting.
In-person presentations will be limited
PO 00000
Frm 00076
Fmt 4703
Sfmt 4703
to three minutes per speaker, with no
more than 15 minutes for all speakers.
Parties interested in making in-person
comments should register on the Public
Comment Registration list available at
the entrance to the meeting location
prior to the beginning of the meeting.
FOR FURTHER INFORMATION CONTACT:
Ginger Norris, National Infrastructure
Advisory Council, Alternate Designated
Federal Officer, Department of
Homeland Security, (703) 235–2888.
SUPPLEMENTARY INFORMATION: Notice of
this meeting is given under the Federal
Advisory Committee Act, 5 U.S.C.
Appendix. The National Infrastructure
Advisory Council shall provide the
President, through the Secretary of
Homeland Security, with advice on the
security and resilience of the Nation’s
critical infrastructure sectors. The NIAC
will meet to discuss issues relevant to
critical infrastructure security and
resilience as directed by the President.
The meeting will commence at 1:30
p.m. EST. At this meeting, the council
will discuss its on-going study on Water
Resilience. All presentations will be
posted prior to the meeting on the
Council’s public Web page—
www.dhs.gov/NIAC.
Public Meeting Agenda
I. Opening of Meeting
II. Roll Call of Members
III. Opening Remarks and Introductions
IV. Approval of Meeting Minutes
V. Status Update on Water Resilience
Working Group
VI. Open Discussion and Public Comment
VII. Closing Remarks
Dated: February 19, 2016.
Ginger Norris,
Alternate Designated Federal Officer for the
National Infrastructure Advisory Council.
[FR Doc. 2016–03925 Filed 2–24–16; 8:45 am]
BILLING CODE 9110–9B–P
DEPARTMENT OF HOMELAND
SECURITY
Transportation Security Administration
Intent To Request Renewal 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
SUMMARY:
E:\FR\FM\25FEN1.SGM
25FEN1
Federal Register / Vol. 81, No. 37 / Thursday, February 25, 2016 / Notices
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 TSAPRA@dhs.gov 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 https://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.
mstockstill on DSK4VPTVN1PROD with NOTICES
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
VerDate Sep<11>2014
18:07 Feb 24, 2016
Jkt 238001
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 TSOC.ST@
dhs.gov 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
PO 00000
Frm 00077
Fmt 4703
Sfmt 4703
9495
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
× 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
DEPARTMENT OF THE INTERIOR
Fish and Wildlife Service
[FWS–R8–ES–2016–N028;
FXES11130800000–167–FF08E00000]
Endangered Species Recovery Permit
Applications
Fish and Wildlife Service,
Interior.
ACTION: Notice of receipt of permit
applications; request for comment.
AGENCY:
We, the U.S. Fish and
Wildlife Service, invite the public to
comment on the following applications
to conduct certain activities with
endangered species. With some
exceptions, the Endangered Species Act
(Act) prohibits activities with
endangered and threatened species
unless a Federal permit allows such
activity. The Act also requires that we
invite public comment before issuing
recovery permits to conduct certain
activities with endangered species.
DATES: Comments on these permit
applications must be received on or
before March 28, 2016.
ADDRESSES: Written data or comments
should be submitted to the Endangered
Species Program Manager, U.S. Fish and
Wildlife Service, Region 8, 2800 Cottage
Way, Room W–2606, Sacramento, CA
95825 (telephone: 916–414–6464; fax:
916–414–6486). Please refer to the
respective permit number for each
application when submitting comments.
FOR FURTHER INFORMATION CONTACT:
Daniel Marquez, Fish and Wildlife
SUMMARY:
E:\FR\FM\25FEN1.SGM
25FEN1
]]>Agencies
[Federal Register Volume 81, Number 37 (Thursday, February 25, 2016)]
[Notices]
[Pages 9494-9495]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[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 TSAPRA@dhs.gov 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 https://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 TSOC.ST@dhs.gov 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
