Gulf of Mexico Fishery Management Council; Public Meeting, 38951-38952 [2013-15508]

Download as PDF Federal Register / Vol. 78, No. 125 / Friday, June 28, 2013 / Notices organization’s overarching policies and processes? 5. How much of your incident handling effort is spent on the different phases of the incident handling lifecycle (from NIST SP 800–61): (1) Preparation, (2) detection-and-analysis, (3) containment-eradication-and-recovery, (4) post-incident-activity. 6. What are the relevant international, sector-specific or de facto standards used or referenced by your organization to support incident handling and related information sharing activities? 7. How do you determine that an incident is in progress (or has happened)? 8. How do you determine that an incident has been handled and requires no further action? 9. How do you determine when to coordinate and/or share information with other organizations regarding an incident? 10. Do you have documented case studies or lessons learned to share (good or bad examples)? If so, please provide URLs or attachments with your response. tkelley on DSK3SPTVN1PROD with NOTICES Organizational Capabilities and Considerations for Effective Incident Coordination Incident handling teams and coordinating centers often collaborate at varying stages of the incident management lifecycle described by NIST SP 800–61. Within this context, individual organizations may offer specific capabilities and may have specific considerations related to effective incident coordination. 1. Do you maintain a list of key contacts for use during an incident? If so, are these contacts identified as individual people, or as positions? 2. What is the size of your organization (e.g. staff, contractors, members)? How many individuals are involved in incident coordination activities carried out by your organization? 3. Relative to the incident response lifecycle defined by NIST SP 800–61, what aspects of incident coordination occur within your organization? 4. What services and assistance (e.g. monitoring, analysis, information) does your organization provide to others both inside and outside your organization relating to incident coordination? 5. Does your organization have any method for understanding and describing the quality or sensitivity of different types of information shared by a third party? For each type of information, can you describe the method? VerDate Mar<15>2010 19:17 Jun 27, 2013 Jkt 229001 6. Approximately how many employees (please indicate full time or part time as appropriate) do you devote to incident response? 7. If possible, list examples of highly effective computer security incident response teams and comment on what made them successful. 8. Based on your personal or your organization’s experience, what are the most and least effective communication mechanisms used (e.g., phone, email, etc.) when coordinating an incident, and why? In what order do you typically use specific communication mechanisms? 9. Do you have examples of alternate communication mechanisms used because an incident has degraded communications? 10. Do you hold regular incident review meetings? Between organizations? How frequently? If your team does not hold incident review meetings regularly, why not? 11. What skillsets (e.g., network sniffing, system administration, firewall configuration, reverse engineering, etc.) does your organization need most when an incident is in progress? 12. Are there incident handling and response skillsets that are specific to your industry or sector? 13. How do those skills relate to information sharing and communication before, during and after an incident? Coordinated Handling of an Incident 1. Do you report incidents or indicators to US–CERT? 2. Do you coordinate incident response with organizations other than US–CERT? 3. Do you participate in an incident coordination community such as the Defense Industrial Base (DIB), the Defense Security Information Exchange (DSIE), or an Information Sharing and Analysis Center (ISAC)? What are the benefits? Are there any pain points? 4. How is information about threats and/or incidents shared among coordination community members? 5. How do you prioritize incidents? 6. How do regulatory requirements affect your organization’s ability or willingness to share information or collaborate during an incident? 7. What regulatory bodies are you required to report information to regarding incidents? For each regulatory body, what kind of information does your organization report and what has been your organization’s reporting experience? Data Handling Considerations 1. What, if any, types of information would create risk or disadvantage if shared by your organization? PO 00000 Frm 00040 Fmt 4703 Sfmt 4703 38951 2. What kinds of information would you never share with a peer during incident handling? 3. What types of protections, redactions, or restrictions would aid your organization in sharing information? 4. Do you use specialized formats to communicate incident information? 5. What do you see as the pros and cons of specialized formats for representing and communicating incident information? 6. What incentives exist for your organization to share information with other organizations during an incident? 7. What disincentives exist that might prevent your organization from sharing information with other organizations during an incident? 8. If available, please provide an example when sharing with other organizations proved to have negative implications for your organization’s incident response. Specific Industry Practices In addition to the approaches above, NIST is interested in identifying core practices that are broadly applicable across sectors and throughout industry. Dated: June 24, 2013. Willie E. May, Associate Director for Laboratory Programs. [FR Doc. 2013–15542 Filed 6–27–13; 8:45 am] BILLING CODE 3510–13–P DEPARTMENT OF COMMERCE National Oceanic and Atmospheric Administration RIN 0648–XC735 Gulf of Mexico Fishery Management Council; Public Meeting National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce. ACTION: Notice of a public meeting. AGENCY: The Gulf of Mexico Fishery Management Council (Council) will hold a meeting of the Council to establish the 2013 red snapper quotas and supplemental recreational red snapper season. The Council will also hold a formal public comment session. DATES: The Council meeting will be held from 7 a.m. until 5 p.m. on Wednesday, July 17, 2013. ADDRESSES: Meeting address: The meeting will be held at the Hilton New Orleans Riverside Hotel, Two Poydras Street, New Orleans, LA 70130; telephone: (504) 561–0500. SUMMARY: E:\FR\FM\28JNN1.SGM 28JNN1 38952 Federal Register / Vol. 78, No. 125 / Friday, June 28, 2013 / Notices tkelley on DSK3SPTVN1PROD with NOTICES Council address: Gulf of Mexico Fishery Management Council, 2203 North Lois Avenue, Suite 1100, Tampa, FL, 33607. FOR FURTHER INFORMATION CONTACT: Mr. Douglas Gregory, Executive Director, Gulf of Mexico Fishery Management Council; telephone: (813) 348–1630; fax: (813) 348–1711; email: doug.gregory@gulfcouncil.org. SUPPLEMENTARY INFORMATION: The items of discussion are as follows: Council Agenda, Wednesday, July 17, 2013, 7 a.m. until 5 p.m. 7 a.m.–7:15 a.m.—Call to Order and Introductions, review the agenda and approve the minutes. 7:15 a.m.–9:30 a.m.—The Council will review an analysis of the yield stream projections for red snapper at constant catch levels. The Council will receive a summary and discuss the proposed actions in the Red Snapper Framework Action. The Council will hear a summary of the written comments received. 9:30 a.m.–12 p.m.—The Council will receive public testimony on the Final Draft of the Framework Action to establish 2013 red snapper quotas and establish the structure of the recreational red snapper season. People wishing to speak before the Council should complete a public comment card prior to the comment period. 1 p.m.–4 p.m.—The Council will select and take final action on the Red Snapper Framework Action to both establish the 2013 red snapper quotas and select the supplemental recreational fishing season structure. 4 p.m.–5 p.m.—The Council will discuss any other business. Although non-emergency issues not contained in this agenda may come before this group for discussion, those issues may not be the subject of formal action during this meeting. Action will be restricted to those issues specifically identified in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Fishery Conservation and Management Act, provided the public has been notified of the Council’s intent to take final action to address the emergency. Special Accommodations The meeting is physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Kathy Pereira at the Council Office (see ADDRESSES), at least 5 working days prior to the meeting. Note: The times and sequence specified in this agenda are subject to change. VerDate Mar<15>2010 19:17 Jun 27, 2013 Jkt 229001 Authority: 16 U.S.C. 1801 et seq. Dated: June 25, 2013. Tracey L. Thompson, Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service. [FR Doc. 2013–15508 Filed 6–27–13; 8:45 am] BILLING CODE 3510–22–P DEPARTMENT OF COMMERCE National Oceanic and Atmospheric Administration RIN 0648–XC518 Endangered Species; File No. 17506 National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce. ACTION: Issuance of permit. AGENCY: Notice is hereby given that Karen G. Holloway-Adkins, East Coast Biologists, Inc. P.O. Box 33715, Indialantic, FL 32903 has been issued a permit to take green (Chelonia mydas), loggerhead (Caretta caretta), hawksbill (Eretmochelys imbricata), Kemp’s ridley (Lepidochelys kempii), and leatherback (Dermochelys coriaceae) sea turtles for purposes of scientific research. ADDRESSES: The permit and related documents are available for review upon written request or by appointment in the following offices: Permits and Conservation Division, Office of Protected Resources, NMFS, 1315 East-West Highway, Room 13705, Silver Spring, MD 20910; phone (301) 427–8401; fax (301) 713–0376; and Southeast Region, NMFS, 263 13th Ave South, St. Petersburg, FL 33701; phone (727) 824–5312; fax (727) 824– 5309. SUMMARY: FOR FURTHER INFORMATION CONTACT: Amy Hapeman or Colette Cairns, (301) 427–8401. SUPPLEMENTARY INFORMATION: On February 28, 2013, notice was published in the Federal Register (78 FR 13642) that a request for a scientific research permit to take green, loggerhead, hawksbill, Kemp’s ridley, and leatherback sea turtles had been submitted by the above-named individual. The requested permit has been issued under the authority of the Endangered Species Act of 1973, as amended (ESA; 16 U.S.C. 1531 et seq.) and the regulations governing the taking, importing, and exporting of endangered and threatened species (50 CFR parts 222–226). Ms. Holloway-Adkins has been issued a 5-year research permit to continue to characterize the population of sea PO 00000 Frm 00041 Fmt 4703 Sfmt 4703 turtles that utilize the nearshore hard bottom reefs in Brevard County, FL. Green and loggerhead sea turtles would be captured, flipper and passive integrated transponder tagged, measured, weighed, tissue and blood sampled and photographed before release. A subset of green sea turtles may be stomach lavaged or have an acoustic transmitter attached to the carapace for tracking movements. Researchers are also authorized to count all sea turtle species during vessel surveys in the nearshore waters of Florida and Georgia. Issuance of this permit, as required by the ESA, was based on a finding that such permit (1) Was applied for in good faith, (2) will not operate to the disadvantage of such endangered or threatened species, and (3) is consistent with the purposes and policies set forth in section 2 of the ESA. Dated: June 25, 2013. P. Michael Payne, Chief, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service. [FR Doc. 2013–15503 Filed 6–27–13; 8:45 am] BILLING CODE 3510–22–P COMMITTEE FOR PURCHASE FROM PEOPLE WHO ARE BLIND OR SEVERELY DISABLED Procurement List; Proposed Additions to and Deletions Committee for Purchase From People Who Are Blind or Severely Disabled. ACTION: Proposed Additions to and Deletions from the Procurement List. AGENCY: The Committee is proposing to add products and services to the Procurement List that will be furnished by nonprofit agencies employing persons who are blind or have other severe disabilities, and deletes services previously furnished by such agencies. Comments Must Be Received On Or Before: 7/29/2013. ADDRESSES: Committee for Purchase From People Who Are Blind or Severely Disabled, 1401 S. Clark Street, Suite 10800, Arlington, Virginia, 22202–4149. For Further Information Or To Submit Comments Contact: Barry S. Lineback, Telephone: (703) 603–7740, Fax: (703) 603–0655, or email CMTEFedReg@AbilityOne.gov. SUMMARY: This notice is published pursuant to 41 U.S.C. 8503 (a)(2) and 41 CFR 51–2.3. Its purpose is to provide interested persons SUPPLEMENTARY INFORMATION: E:\FR\FM\28JNN1.SGM 28JNN1

Agencies

[Federal Register Volume 78, Number 125 (Friday, June 28, 2013)]
[Notices]
[Pages 38951-38952]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: 2013-15508]


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

DEPARTMENT OF COMMERCE

National Oceanic and Atmospheric Administration

RIN 0648-XC735


Gulf of Mexico Fishery Management Council; Public Meeting

AGENCY: National Marine Fisheries Service (NMFS), National Oceanic and 
Atmospheric Administration (NOAA), Commerce.

ACTION: Notice of a public meeting.

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

SUMMARY: The Gulf of Mexico Fishery Management Council (Council) will 
hold a meeting of the Council to establish the 2013 red snapper quotas 
and supplemental recreational red snapper season. The Council will also 
hold a formal public comment session.

DATES: The Council meeting will be held from 7 a.m. until 5 p.m. on 
Wednesday, July 17, 2013.

ADDRESSES: Meeting address: The meeting will be held at the Hilton New 
Orleans Riverside Hotel, Two Poydras Street, New Orleans, LA 70130; 
telephone: (504) 561-0500.

[[Page 38952]]

    Council address: Gulf of Mexico Fishery Management Council, 2203 
North Lois Avenue, Suite 1100, Tampa, FL, 33607.

FOR FURTHER INFORMATION CONTACT: Mr. Douglas Gregory, Executive 
Director, Gulf of Mexico Fishery Management Council; telephone: (813) 
348-1630; fax: (813) 348-1711; email: doug.gregory@gulfcouncil.org.

SUPPLEMENTARY INFORMATION: The items of discussion are as follows:

Council Agenda, Wednesday, July 17, 2013, 7 a.m. until 5 p.m.

    7 a.m.-7:15 a.m.--Call to Order and Introductions, review the 
agenda and approve the minutes.
    7:15 a.m.-9:30 a.m.--The Council will review an analysis of the 
yield stream projections for red snapper at constant catch levels. The 
Council will receive a summary and discuss the proposed actions in the 
Red Snapper Framework Action. The Council will hear a summary of the 
written comments received.
    9:30 a.m.-12 p.m.--The Council will receive public testimony on the 
Final Draft of the Framework Action to establish 2013 red snapper 
quotas and establish the structure of the recreational red snapper 
season. People wishing to speak before the Council should complete a 
public comment card prior to the comment period.
    1 p.m.-4 p.m.--The Council will select and take final action on the 
Red Snapper Framework Action to both establish the 2013 red snapper 
quotas and select the supplemental recreational fishing season 
structure.
    4 p.m.-5 p.m.--The Council will discuss any other business.
    Although non-emergency issues not contained in this agenda may come 
before this group for discussion, those issues may not be the subject 
of formal action during this meeting. Action will be restricted to 
those issues specifically identified in this notice and any issues 
arising after publication of this notice that require emergency action 
under section 305(c) of the Magnuson-Stevens Fishery Conservation and 
Management Act, provided the public has been notified of the Council's 
intent to take final action to address the emergency.

Special Accommodations

    The meeting is physically accessible to people with disabilities. 
Requests for sign language interpretation or other auxiliary aids 
should be directed to Kathy Pereira at the Council Office (see 
ADDRESSES), at least 5 working days prior to the meeting.

    Note: The times and sequence specified in this agenda are 
subject to change.


    Authority: 16 U.S.C. 1801 et seq.

    Dated: June 25, 2013.
Tracey L. Thompson,
Acting Deputy Director, Office of Sustainable Fisheries, National 
Marine Fisheries Service.
[FR Doc. 2013-15508 Filed 6-27-13; 8:45 am]
BILLING CODE 3510-22-P
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.