Software Assurance Program: Building Better Quality and More Secure Software, 5351-5352 [E6-1346]

Download as PDF Federal Register / Vol. 71, No. 21 / Wednesday, February 1, 2006 / Notices cchase on PROD1PC60 with NOTICES Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3192, MSC 7848, Bethesda, MD 20892, 301–435– 2309, pluded@csr.nih.gov. Name of Committee: Respiratory Sciences Integrated Review Group, Lung Cellular, Molecular, and Immunobiology Study Section. Date: February 22–23, 2006. Time: 8 a.m. to 6 p.m. Agenda: To review and evaluate grant applications. Place: Wyndham City Center Hotel, 1143 New Hampshire Ave., NW., Washington, DC 20037. Contact Person: George M. Barnas, PhD., Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2180, MSC 7818, Bethesda, MD 20892, 301–435– 0696, barnasg@csr.nih.gov. Name of Committee: Oncological Sciences Integrated Review Group, Chemo/Dietary Prevention Study Section. Date: February 22–24, 2006. Time: 5 p.m. to 5 p.m. Agenda: To review and evaluate grant applications. Place: Latham Hotel, 3000 M Street, NW., Washington, DC 20007. Contact Person: Sally A. Mulhern, PhD., Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6198, MSC 7804, Bethesda, MD 20892, (301) 435– 5877, mulherns@csr.nih.gov. Name of Committee: Brain Disorders and Clinical Neuroscience Integrated Review Group, Neural Basis of Psychopathology, Addictions and Sleep Disorders Study Section. Date: February 22–24, 2006. Time: 6 p.m. to 2 p.m. Agenda: To review and evaluate grant applications. Place: St. Gregory Hotel, 2033 M Street, NW., Washington, DC 20036. Contact Person: Julius Cinque, MS., Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5186, MSC 7846, Bethesda, MD 20892, (301) 435– 1252, cinquej@csr.nih.gov. (Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393–93.396, 93.837–93.844, 93.846–93.878, 93.892, 93.893, National Institutes of Health, HHS.) Dated: January 24, 2006. Anna Snouffer, Acting Director, Office of Federal Advisory Committee Policy. [FR Doc. 06–919 Filed 1–31–06; 8:45 am] BILLING CODE 4140–01–M VerDate Aug<31>2005 17:49 Jan 31, 2006 Jkt 208001 DEPARTMENT OF HEALTH AND HUMAN SERVICES National Institutes of Health Prospective Grant of an Exclusive License: ‘‘Vasostatin as Marrow Protectant’’ and ‘‘Use of Calreticulin and Calreticulin Fragments To Inhibit Endothelial Cell Growth and Angiogenesis and Suppress Tumor Growth’’ National Institutes of Health, Public Health Service, HHS. ACTION: Notice. AGENCY: SUMMARY: This notice, in accordance with 35 U.S.C. 209(c)(1) and 37 CFR 404.7(a)(1) (i), announces that the Department of Health and Human Services is contemplating the grant of an exclusive license to practice the inventions embodied in U.S. Patent No. 6,596,690 B2 entitled ‘‘Vasostatin as Marrow Protectant’’ (HHS Reference E– 230–2000/0); U.S. Patent Application No. 09/807,148 filed April 5, 2001, entitled ‘‘Use of Calreticulin and Calreticulin Fragments To Inhibit Endothelial Cell Growth and Angiogenesis and Suppress Tumor Growth’’ (HHS Reference E–082–1998/ 0–US–03); PCT Application No. PCT/ US99/23240 filed October 5, 1999 entitled ‘‘Use of Calreticulin and Calreticulin Fragments To Inhibit Endothelial Cell Growth and Angiogenesis and Suppress Tumor Growth’’ (HHS Reference E–082–1998/ 0–PCT–02); to RxKinetix, Inc. The patent rights in these inventions have been assigned to the United States of America. The prospective exclusive license territory may be worldwide and the field of use may be limited to development and sale of a pharmaceutical product useful in protecting bone marrow stem cells from the toxic effects of chemotherapy and radiotherapy. DATES: Only written comments and/or license applications which are received by the National Institutes of Health on or before April 3, 2006 will be considered. ADDRESSES: Requests for copies of the patent and/or patent applications, inquiries, comments and other materials relating to the contemplated exclusive license should be directed to: Mojdeh Bahar, J.D., Technology Licensing Specialist, Office of Technology Transfer, National Institutes of Health, 6011 Executive Boulevard, Suite 325, Rockville, MD 20852–3804. Telephone: (301) 435–2950; Facsimile: (301) 402– 0220; E-mail: baharm@od.nih.gov. PO 00000 Frm 00120 Fmt 4703 Sfmt 4703 5351 The technology claimed in the aforementioned patents is based on the discovery of the calreticulin N-domain (vasostatin) and the three previously uncharacterized properties of calreticulin. First, calreticulin N-domain is shown to stimulate the proliferation and survival in vitro of hematopoietic cells in the presence of previously identified growth factors. Second, Vasostatin is shown to protect hematopoietic cells in vitro from toxicity induced by a variety of chemotherapeutic agents. Third, Vasostatin is shown to protect a subject from toxicity to the hematopoietic system induced by chemotherapy or irradiation. The prospective exclusive license will be royalty-bearing and will comply with the terms and conditions of 35 U.S.C. 209 and 37 CFR 404.7. The prospective exclusive license may be granted unless within sixty (60) days from the date of this published notice, the NIH receives written evidence and argument that establish that the grant of the license would not be consistent with the requirements of 35 U.S.C. 209 and 37 CFR 404.7. Applications for a license in the field of use filed in response to this notice will be treated as objections to the grant of the contemplated exclusive license. Comments and objections submitted to this notice will not be made available for public inspection and, to the extent permitted by law, will not be released under the Freedom of Information Act, 5 U.S.C. 552. This is a modification to the notice published in 70 FR 96, January 3, 2005. SUPPLEMENTARY INFORMATION: Dated: January 23, 2006. Steven M. Ferguson, Director, Division of Technology Development and Transfer, Office of Technology Transfer, National Institutes of Health. [FR Doc. E6–1389 Filed 1–31–06; 8:45 am] BILLING CODE 4140–01–P DEPARTMENT OF HOMELAND SECURITY Office of the Secretary [Docket No. DHS–2005–0057] Software Assurance Program: Building Better Quality and More Secure Software National Cyber Security Division, DHS. ACTION: Notice of availability. AGENCY: SUMMARY: The purpose of this notice is to inform the public and interested E:\FR\FM\01FEN1.SGM 01FEN1 cchase on PROD1PC60 with NOTICES 5352 Federal Register / Vol. 71, No. 21 / Wednesday, February 1, 2006 / Notices security partners that two draft documents are being released by the Department of Homeland Security (DHS) for comment prior to publication: • Security in the Software Lifecycle— Intended to assist application software developers and project managers in defining a strategy to produce more secure software. • Secure Software Assurance— Common Body of Knowledge—Intended to assist college-level educators and private industry trainers in creating a curriculum for software assurance. ADDRESSES: If you would like to review the draft Security in the Software Lifecycle and the draft Secure Software Assurance—Common Body of Knowledge you may access the documents and the comment forms through one of the following methods: • Build Security In Web site: https:// buildsecurityin.us-cert.gov—click on ‘‘Additional Resources’’ Tab. The documents are located in the ‘‘Supplementary Department of Homeland Security Resources’’ and ‘‘Software Assurance Common Body of Knowledge (CBK)’’ sections. • Mail self-addressed stamped envelope to: Joe Jarzombek, Director for Software Assurance, National Cyber Security Division, Department of Homeland Security, Washington, DC 20528 (Postage: $5.00 for one document/ $8.00 for both documents). If you desire to submit comments, they must be received by February 21, 2006. A comment form is available on the Build Security In Web site (https:// buildsecurityin.us-cert.gov) to facilitate detailed comments. Comments must be identified by DHS–2005–0057 and submitted by one of the following methods: • Federal eRulemaking Portal: https:// www.regulations.gov. Refer to Docket DHS–2005–0057. Follow the instructions for submitting comments. Detailed comment forms can be uploaded. • Mail: Joe Jarzombek, Director for Software Assurance, National Cyber Security Division, Department of Homeland Security, Washington, DC 20528. FOR FURTHER INFORMATION CONTACT: DHS Software Assurance Program: Joe Jarzombek, Director for Software Assurance, National Cyber Security Division, Department of Homeland Security, Washington, DC 20528, 703– 235–5126 or joe.jarzombek@dhs.gov. SUPPLEMENTARY INFORMATION: In collaboration with other government agencies, academia, and private industry, DHS seeks to reduce software vulnerabilities, minimize exploitation, VerDate Aug<31>2005 17:49 Jan 31, 2006 Jkt 208001 and address means to improve capabilities to routinely develop and deploy quality and trustworthy software. In furtherance of those goals, DHS established the Software Assurance Program. The DHS Software Assurance Program is grounded in the National Strategy to Secure Cyberspace issued by President Bush in February 2003. DHS began the Software Assurance Program as a focal point to partner with the private sector, academia, and other government agencies in order to improve software development and acquisition processes. The Program seeks to reduce software vulnerabilities, minimize exploitation, and address means to improve capabilities to routinely develop and deploy quality and trustworthy software products—enabling more resilient assets within the critical infrastructure. DHS developed the following comprehensive approach to address software assurance in collaboration with industry, academia, and government partners: • People—Focus on software developers (includes education and training) and users • Process—Focus on developing sound practices and practical guidelines • Technology—Focus on software evaluation tools and R&D requirements • Acquisition—Focus on standards, specifications, acquisition language As part of the Software Assurance Program, DHS now seeks comments from the public and interested security partners on two draft documents now being released prior to formal publication: • Security in the Software Lifecycle— Intended for application software developers and project managers who wish to increase their understanding of security and quality issues related to software and its production, and to improve their own practices in order to produce more secure and better quality application software. This document should provide enough information to assist the reader in defining a strategy for adapting or expanding existing processes and practices to produce more secure software that also achieves a higher degree of quality, reliability, and integrity. • Secure Software Assurance— Common Body of Knowledge—Primarily intended for college-level educators and private industry trainers to use as they create curriculum for software assurance which draws upon multi-disciplinary elements of software engineering, information assurance, project management, systems engineering, safety and security, and acquisition. While some of these disciplines already PO 00000 Frm 00121 Fmt 4703 Sfmt 4703 have a body of knowledge, software assurance has not had a formal source for educators to create curriculum. This document is intended to fill that need. The information in these documents is not intended to represent a standard or policy mandate by DHS. On the contrary, the documents represent a collection of consensus-based, ‘‘sound practices’’ derived from across government, industry, and academia, both in the U.S. and abroad. As such, they should be seen primarily as tools for educating developers and software project managers. DHS will consider all timely and pertinent comments received prior to finalizing these documents. Dated: January 23, 2006. Robert B. Stephan, Assistant Secretary for Infrastructure Protection. [FR Doc. E6–1346 Filed 1–31–06; 8:45 am] BILLING CODE 4410–10–P DEPARTMENT OF HOMELAND SECURITY Coast Guard [USCG–2006–23696] Towing Safety Advisory Committee Coast Guard, DHS. Notice of meetings. AGENCY: ACTION: SUMMARY: The Towing Safety Advisory Committee (TSAC) and its working groups will meet as required to discuss various issues relating to shallow-draft inland and coastal waterway navigation and towing safety. All meetings will be open to the public. DATES: TSAC will meet on Thursday, March 2, 2006, from 8 a.m. to 3:30 p.m. The Towing Vessel Inspection Working Group will meet on Tuesday, February 28, 2006, from 9 a.m. to 4:30 p.m. The Towing Vessel Inspection Working Group will meet again on Wednesday, March 1, 2006, from 8:30 a.m. to 2:30 p.m. followed by a general plenary meeting, to discuss the status of other working groups, until 5 p.m. These meetings may close early if all business is finished. Written material for and requests to make oral presentations at the meetings should reach the Coast Guard on or before February 21, 2006. Requests to have a copy of your material distributed to each member of the Committee or working groups prior to the meetings should reach the Coast Guard on or before February 15, 2006. ADDRESSES: TSAC will meet in Room 2415, U.S. Coast Guard Headquarters, 2100 Second Street, SW., Washington, E:\FR\FM\01FEN1.SGM 01FEN1

Agencies

[Federal Register Volume 71, Number 21 (Wednesday, February 1, 2006)]
[Notices]
[Pages 5351-5352]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: E6-1346]


=======================================================================
-----------------------------------------------------------------------

DEPARTMENT OF HOMELAND SECURITY

Office of the Secretary

[Docket No. DHS-2005-0057]


Software Assurance Program: Building Better Quality and More 
Secure Software

AGENCY: National Cyber Security Division, DHS.

ACTION: Notice of availability.

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

SUMMARY: The purpose of this notice is to inform the public and 
interested

[[Page 5352]]

security partners that two draft documents are being released by the 
Department of Homeland Security (DHS) for comment prior to publication:
     Security in the Software Lifecycle--Intended to assist 
application software developers and project managers in defining a 
strategy to produce more secure software.
     Secure Software Assurance--Common Body of Knowledge--
Intended to assist college-level educators and private industry 
trainers in creating a curriculum for software assurance.

ADDRESSES: If you would like to review the draft Security in the 
Software Lifecycle and the draft Secure Software Assurance--Common Body 
of Knowledge you may access the documents and the comment forms through 
one of the following methods:
     Build Security In Web site: https://buildsecurityin.us-
cert.gov click on ``Additional Resources'' Tab. The documents are 
located in the ``Supplementary Department of Homeland Security 
Resources'' and ``Software Assurance Common Body of Knowledge (CBK)'' 
sections.
     Mail self-addressed stamped envelope to: Joe Jarzombek, 
Director for Software Assurance, National Cyber Security Division, 
Department of Homeland Security, Washington, DC 20528 (Postage: $5.00 
for one document/$8.00 for both documents).
    If you desire to submit comments, they must be received by February 
21, 2006. A comment form is available on the Build Security In Web site 
(https://buildsecurityin.us-cert.gov) to facilitate detailed comments. 
Comments must be identified by DHS-2005-0057 and submitted by one of 
the following methods:
     Federal eRulemaking Portal: https://www.regulations.gov. 
Refer to Docket DHS-2005-0057. Follow the instructions for submitting 
comments. Detailed comment forms can be uploaded.
     Mail: Joe Jarzombek, Director for Software Assurance, 
National Cyber Security Division, Department of Homeland Security, 
Washington, DC 20528.

FOR FURTHER INFORMATION CONTACT: DHS Software Assurance Program: Joe 
Jarzombek, Director for Software Assurance, National Cyber Security 
Division, Department of Homeland Security, Washington, DC 20528, 703-
235-5126 or joe.jarzombek@dhs.gov.

SUPPLEMENTARY INFORMATION: In collaboration with other government 
agencies, academia, and private industry, DHS seeks to reduce software 
vulnerabilities, minimize exploitation, and address means to improve 
capabilities to routinely develop and deploy quality and trustworthy 
software. In furtherance of those goals, DHS established the Software 
Assurance Program.
    The DHS Software Assurance Program is grounded in the National 
Strategy to Secure Cyberspace issued by President Bush in February 
2003. DHS began the Software Assurance Program as a focal point to 
partner with the private sector, academia, and other government 
agencies in order to improve software development and acquisition 
processes. The Program seeks to reduce software vulnerabilities, 
minimize exploitation, and address means to improve capabilities to 
routinely develop and deploy quality and trustworthy software 
products--enabling more resilient assets within the critical 
infrastructure.
    DHS developed the following comprehensive approach to address 
software assurance in collaboration with industry, academia, and 
government partners:
     People--Focus on software developers (includes education 
and training) and users
     Process--Focus on developing sound practices and practical 
guidelines
     Technology--Focus on software evaluation tools and R&D 
requirements
     Acquisition--Focus on standards, specifications, 
acquisition language
    As part of the Software Assurance Program, DHS now seeks comments 
from the public and interested security partners on two draft documents 
now being released prior to formal publication:
     Security in the Software Lifecycle--Intended for 
application software developers and project managers who wish to 
increase their understanding of security and quality issues related to 
software and its production, and to improve their own practices in 
order to produce more secure and better quality application software. 
This document should provide enough information to assist the reader in 
defining a strategy for adapting or expanding existing processes and 
practices to produce more secure software that also achieves a higher 
degree of quality, reliability, and integrity.
     Secure Software Assurance--Common Body of Knowledge--
Primarily intended for college-level educators and private industry 
trainers to use as they create curriculum for software assurance which 
draws upon multi-disciplinary elements of software engineering, 
information assurance, project management, systems engineering, safety 
and security, and acquisition. While some of these disciplines already 
have a body of knowledge, software assurance has not had a formal 
source for educators to create curriculum. This document is intended to 
fill that need.
    The information in these documents is not intended to represent a 
standard or policy mandate by DHS. On the contrary, the documents 
represent a collection of consensus-based, ``sound practices'' derived 
from across government, industry, and academia, both in the U.S. and 
abroad. As such, they should be seen primarily as tools for educating 
developers and software project managers.
    DHS will consider all timely and pertinent comments received prior 
to finalizing these documents.

    Dated: January 23, 2006.
Robert B. Stephan,
Assistant Secretary for Infrastructure Protection.
 [FR Doc. E6-1346 Filed 1-31-06; 8:45 am]
BILLING CODE 4410-10-P
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.