One document matched: draft-ietf-opsec-efforts-09.xml
<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<rfc catagory="inf" ipr="full3978" docName="draft-ietf-opsec-efforts-09.txt">
<front>
<title abbrev='Security Efforts and Documents'>
Security Best Practices Efforts and Documents
</title>
<author initials="C.M." surname="Lonvick"
fullname="Chris Lonvick">
<organization>Cisco Systems</organization>
<address>
<postal>
<street>12515 Research Blvd.</street>
<city>Austin</city><region>Texas</region>
<code>78759</code>
<country>US</country>
</postal>
<phone>+1 512 378 1182</phone>
<email>clonvick@cisco.com</email>
</address>
</author>
<author initials="D." surname="Spak"
fullname="David Spak">
<organization>Cisco Systems</organization>
<address>
<postal>
<street>12515 Research Blvd.</street>
<city>Austin</city><region>Texas</region>
<code>78759</code>
<country>US</country>
</postal>
<phone>+1 512 378 1720</phone>
<email>dspak@cisco.com</email>
</address>
</author>
<date month="December" year="2008" />
<keyword>Security</keyword>
<keyword>Standards</keyword>
<keyword>SDO</keyword>
<keyword>Standards Developing Organization</keyword>
<abstract>
<t>
This document provides a snapshot of the current efforts to define or
apply security requirements in various Standards Developing Organizations (SDO).
</t>
</abstract>
</front>
<middle>
<section anchor="intro" title="Introduction">
<t>
The Internet is being recognized as a critical infrastructure similar in nature to
the power grid and a potable water supply. Just like those infrastructures, means are
needed to provide resiliency and adaptability to the Internet so that it remains
consistently available to the public throughout the world even during times of
duress or attack. For this reason, many SDOs are
developing standards with hopes of retaining an acceptable level, or even improving
this availability, to its users.
These SDO efforts usually define themselves as "security" efforts. It is the opinion
of the authors that there are many different definitions of the term "security" and
it may be applied in many diverse ways. As such, we offer no assurance that the
term is applied consistently throughout this document.
</t>
<t>
Many of these SDOs have diverse charters and goals and will take entirely different
directions in their efforts to provide standards. However, even with that, there
will be overlaps in their produced works. If there are overlaps then there is a
potential for conflicts and confusion. This may result in:
<list>
<t>
Vendors of networking equipment who are unsure of which standard to follow.
</t>
<t>
Purchasers of networking equipment who are unsure of which standard will
best apply to the needs of their business or ogranization.
</t>
<t>
Network Administrators and Operators unsure of which standard to follow
to attain the best security for their network.
</t>
</list>
For these reasons, the authors wish to encourage all SDOs who have an interest
in producing or in consuming standards relating to good security practices to
be consistent in their approach and their recommendations. In many cases, the
authors are aware that the SDOs are making good efforts along these lines.
However, the authors do not participate in all SDO efforts and cannot know
everything that is happening.
</t>
<t>
The OpSec Working Group met at the 61st IETF and agreed that this document
could be a useful reference in producing the documents described in the
Working Group Charter. The authors have agreed to keep this document current
and request that those who read it will submit corrections or comments.
</t>
<t>
Comments on this document may be addressed to the OpSec Working Group or
directly to the authors.
<list>
<t>
opsec@ops.ietf.org
</t>
</list>
</t>
</section>
<section anchor="format" title="Format of this Document">
<t>
The body of this document has three sections.
</t>
<t>
The first part of the body of this document, <xref target="glossaries" />,
contains a listing of online glossaries relating to networking
and security. It is very important that the definitions of words relating to
security and security events be consistent. Inconsistencies between the useage
of words on standards is unacceptable as it would prevent a reader of two
standards to appropriately relate their recommendations. The authors of this
document have not reviewed the definitions of the words in the listed glossaries
so can offer no assurance of their alignment.
</t>
<t>
The second part, <xref target="sdo" />, contains a listing of SDOs
that appear to be working on security standards.
</t>
<t>
The third part, <xref target="docs" />, lists the documents which have been found to offer good practices
or recommendations for securing networks and networking devices.
</t>
</section>
<section anchor="glossaries" title="Online Security Glossaries">
<t>
This section contains references to glossaries of network and computer security terms
</t>
<section anchor="atis2kglossary" title="ATIS Telecom Glossary 2000">
<t>
http://www.atis.org/tg2k/
</t>
<t>
Under an approved T1 standards project (T1A1-20), an existing 5800-entry,
search-enabled hypertext telecommunications glossary titled Federal Standard
1037C, Glossary of Telecommunication Terms was updated and matured into this
glossary, T1.523-2001, Telecom Glossary 2000. This updated glossary was
posted on the Web as an American National Standard (ANS).
</t>
</section>
<section anchor="ietfgloss" title="Internet Security Glossary - RFC 4949">
<t>
http://www.ietf.org/rfc/rfc4949.txt
</t>
<t>
This document was originally created as RFC 2828 in May 2000.
It was revised as RFC 4949 and the document defines itself to be,
"an internally consistent, complementary set of abbreviations, definitions,
explanations, and recommendations for use of terminology related to
information system security."
</t>
</section>
<section anchor="itugloss" title="Compendium of Approved ITU-T Security Definitions">
<t>
http://www.itu.int/itudoc/itu-t/com17/activity/def004.html
</t>
<t>
Addendum to the Compendium of the Approved ITU-T Security-related Definitions
http://www.itu.int/itudoc/itu-t/com17/activity/add002.html
</t>
<t>
These extensive materials were created from approved ITU-T Recommendations with
a view toward establishing a common understanding and use of security terms within ITU-T.
</t>
</section>
<section anchor="MSglossary" title="Microsoft Solutions for Security Glossary">
<t>
http://www.microsoft.com/security/glossary.mspx
</t>
<t>
The Microsoft Solutions for Security Glossary was created to explain the
concepts, technologies, and products associated with computer security. This
glossary contains several definitions specific to Microsoft proprietary
technologies and product solutions.
</t>
</section>
<section anchor="sans" title="SANS Glossary of Security Terms">
<t>
http://www.sans.org/resources/glossary.php
</t>
<t>
The SANS Institute (SysAdmin, Audit, Network, Security) was created in 1989
as, "a cooperative research and education organization." Updated in May
2003, SANS cites the NSA for their help in creating the online glossary of
security terms. The SANS Institute is also home to many other resources
including the SANS Intrusion Detection FAQ and the SANS/FBI Top 20 Vulnerabilities
List.
</t>
</section>
<section anchor="wheeler" title="Security Taxonomy and Glossary - Anne & Lynn Wheeler">
<t>
http://www.garlic.com/~lynn/secure.htm
</t>
<t>
Anne and Lynn Wheeler maintain a security taxonomy and glossary with terms merged from AFSEC, AJP, CC1, CC2, CC21 (CC site), CIAO, FCv1, FFIEC, FJC, FTC, IATF V3 (IATF site), IEEE610, ITSEC, Intel, JTC1/SC27 (SC27 site), KeyAll, MSC, NIST 800-30, 800-33, 800-37, 800-53, 800-61, 800-77, 800-83 FIPS140, NASA, NCSC/TG004, NIAP, NSA Intrusion, CNSSI 4009, online security study, RFC1983, RFC2504, RFC2647, RFC2828, TCSEC, TDI, and TNI.
</t>
</section>
</section>
<section anchor="sdo" title="Standards Developing Organizations">
<t>
This section of this document lists the SDOs, or organizations that appear to be
developing security related standards. These SDOs are listed in alphabetical order.
</t>
<t>
Note: The authors would appreciate corrections and additions. This
note will be removed before publication as an RFC.
</t>
<section anchor="3gpp" title="3GPP - Third Generation Partnership Project">
<t>
http://www.3gpp.org/
</t>
<t>
The 3rd Generation Partnership Project (3GPP) is a collaboration agreement
formed in December 1998. The collaboration agreement is comprised of several
telecommunications standards bodies which are known as "Organizational
Partners". The current Organizational Partners involved with 3GPP are ARIB,
CCSA, ETSI, ATIS, TTA, and TTC.
</t>
</section>
<section anchor="3gpp2" title="3GPP2 - Third Generation Partnership Project 2">
<t>
http://www.3gpp2.org/
</t>
<t>
Third Generation Partnership Project 2 (3GPP2) is a collaboration among
Organizational Partners much like its sister project 3GPP. The Organizational
Partners (OPs) currently involved with 3GPP2 are ARIB, CCSA, TIA, TTA, and TTC. In
addition to the OPs, 3GPP2 also welcomes the CDMA Development Group and IPv6
Forum as Market Representation Partners for market advice.
</t>
</section>
<section anchor="ansi" title="ANSI - The American National Standards Institute">
<t>
http://www.ansi.org/
</t>
<t>
ANSI is a private, non-profit organization that organizes and oversees the
U.S. voluntary standardization and conformity assessment system. ANSI was
founded October 19, 1918.
</t>
<section anchor="x9" title="Accredited Standards Committee X9 (ASC X9)">
<t>
http://www.x9.org/
</t>
<t>
The Accredited Standards Committee X9 (ASC X9) has the mission to develop, establish, maintain, and promote standards for the Financial Services Industry in order to facilitate delivery of financial services and products.
</t>
</section>
</section>
<section anchor="atis" title="ATIS - Alliance for Telecommunications Industry Solutions">
<t>
http://www.atis.org/
</t>
<t>
ATIS is a United States based body that is committed to rapidly developing and
promoting technical and operations standards for the communications and
related information technologies industry worldwide using pragmatic, flexible
and open approach. Committee T1 as a group no longer exists as a result of
the recent ATIS reorganization on January 1, 2004. ATIS has restructured the
former T1 technical subcommittees into full ATIS standards committees to
easily identify and promote the nature of standards work each committee
performs. Due to the reorganization, some groups may have a new mission and
scope statement.
</t>
<section anchor="nipp" title="ATIS NIPP - Network Interface, Power, and Protection
Committee, formerly T1E1">
<t>
http://www.atis.org/0050/index.asp
</t>
<t>
ATIS Network Interface, Power, and Protection Committee develops and
recommends standards and technical reports related to power systems,
electrical and physical protection for the exchange and interexchange
carrier networks, and interfaces associated with user access to
telecommunications networks. </t>
</section>
<section anchor="nprq" title="ATIS NPRQ - Network Performance, Reliability, and
Quality of Service Committee, formerly T1A1">
<t>
http://www.atis.org/0010/index.asp
</t>
<t>
ATIS Network Performance, Reliability and Quality of Service Committee
develops and recommends standards, requirements, and technical reports
related to the performance, reliability, and associated security
aspects of communications networks, as well as the processing of
voice, audio, data, image, and video signals, and their multimedia
integration.
</t>
</section>
<section anchor="obf" title="ATIS OBF - Ordering and Billing Forum, formerly regarding T1M1
O&B">
<t>
http://www.atis.org/obf/index.asp
</t>
<t>
The T1M1 O&B subcommittee has become part of the ATIS Ordering and
Billing Forum.
</t>
<t>
The ATIS-sponsored Ordering and Billing Forum (OBF) provides a forum
for customers and providers in the telecommunications industry to
identify, discuss and resolve national issues which affect ordering,
billing, provisioning and exchange of information about access
services, other connectivity and related matters.
</t>
</section>
<section anchor="optxs" title="ATIS OPTXS - Optical Transport and Synchronization
Committee, formerly T1X1">
<t>
http://www.atis.org/0240/index.asp
</t>
<t>
ATIS Optical Transport and Synchronization Committee develops and
recommends standards and prepares technical reports related to
telecommunications network technology pertaining to network
synchronization interfaces and hierarchical structures including
optical technology.
</t>
</section>
<section anchor="tmoc" title="ATIS TMOC - Telecom Management and Operations
Committee, formerly T1M1 OAM&P">
<t>
http://www.atis.org/0130/index.asp
</t>
<t>
ATIS Telecom Management and Operations Committee develops internetwork
operations, administration, maintenance and provisioning standards,
and technical reports related to interfaces for telecommunications
networks. </t>
</section>
<section anchor="wtsc" title="ATIS WTSC - Wireless Technologies and Systems
Committee, formerly T1P1">
<t>
http://www.atis.org/0160/index.asp
</t>
<t>
ATIS Wireless Technologies and Systems Committee develops and
recommends standards and technical reports related to wireless and/or
mobile services and systems, including service descriptions and
wireless technologies. </t>
</section>
<section anchor="ptsc" title="ATIS PTSC - Packet Technologies and Systems Committee,
formerly T1S1">
<t>
http://www.atis.org/0191/index.asp
</t>
<t>
T1S1 was split into two separate ATIS committees: the ATIS Packet
Technologies and Systems Committee and the ATIS Protocol Interworking
Committee. PTSC is responsible for producing standards to secure
signalling.
</t>
<t>
The basic document is PTSC-SEC-2005-059.doc which is in Letter Ballot
at this time. It is expected to move to an ANSI standard.
</t>
</section>
<section anchor="ATISpic" title="ATIS Protocol Interworking Committee, regarding T1S1">
<t>
T1S1 was split into two separate ATIS committees: the ATIS Packet
Technologies and Systems Committee and the ATIS Protocol Interworking
Committee. As a result of the reorganization of T1S1, these groups will
also probably have a new mission and scope.
</t>
</section>
</section>
<section anchor="cc" title="CC - Common Criteria">
<t>
http://www.commoncriteriaportal.org/
</t>
<t>
In June 1993, the sponsoring organizations of the existing US, Canadian, and European
criterias (TCSEC, ITSEC, and similar) started the Common Criteria Project to align their
separate criteria into a single set of IT security criteria.
</t>
</section>
<section anchor="dmtf" title="DMTF - Distributed Management Task Force, Inc.">
<t>
http://www.dmtf.org/
</t>
<t>
Founded in 1992, the DMTF brings the technology industry's customers and top
vendors together in a collaborative, working group approach that involves DMTF
members in all aspects of specification development and refinement.
</t>
</section>
<section anchor="etsi" title="ETSI - The European Telecommunications Standard Institute">
<t>
http://www.etsi.org/
</t>
<t>
ETSI is an independent, non-profit organization which produces telecommunications standards.
ETSI is based in Sophia-Antipolis in the south of France and maintains a membership from 55
countries.
</t>
<t>
Joint work between ETSI and ITU-T SG-17
</t>
<t>
http://www.tta.or.kr/gsc/upload/GSC9_Joint_011_Security_Standardization_in_ITU.ppt
</t>
</section>
<section anchor="ggf" title="GGF - Global Grid Forum">
<t>
http://www.gridforum.org/
</t>
<t>
The Global Grid Forum (GGF) is a community-initiated forum of thousands of
individuals from industry and research leading the global standardization
effort for grid computing. GGF's primary objectives are to promote and
support the development, deployment, and implementation of grid technologies
and applications via the creation and documentation of "best practices" -
technical specifications, user experiences, and implementation guidelines.
</t>
</section>
<section anchor="ieee" title="IEEE - The Institute of Electrical and Electronics Engineers, Inc.">
<t>
http://www.ieee.org/
</t>
<t>
IEEE is a non-profit, professional association of more than 360,000 individual
members in approximately 175 countries. The IEEE produces 30 percent of the world's
published literature in electrical engineering, computers, and control technology through
its technical publishing, conferences, and consensus-based standards activities.
</t>
</section>
<section anchor="ietforg" title="IETF - The Internet Engineering Task Force">
<t>
http://www.ietf.org/
</t>
<t>
IETF is a large, international community open to any interested individual
concerned with the evolution of the Internet architecture and the smooth
operation of the Internet.
</t>
</section>
<section anchor="incits" title="INCITS - InterNational Committee for Information Technology
Standards">
<t>
http://www.incits.org/
</t>
<t>
INCITS focuses upon standardization in the field of Information and Communications
Technologies (ICT), encompassing storage, processing, transfer, display, management,
organization, and retrieval of information.
</t>
<section anchor="incitsT11" title="INCITS Technical Committee T11 - Fibre Channel Interfaces">
<t>
http://www.t11.org/index.htm
</t>
<t>
T11 is responsible for standards development in the areas of Intelligent Peripheral
Interface (IPI), High-Performance Parallel Interface (HIPPI) and Fibre Channel (FC).
T11 has a project called FC-SP to define Security Protocols for Fibre Channel.
</t>
<t>
FC-SP Project Proposal: ftp://ftp.t11.org/t11/admin/project_proposals/02-036v2.pdf
</t>
</section>
</section>
<section anchor="iso" title="ISO - The International Organization for Standardization">
<t>
http://www.iso.org/
</t>
<t>
ISO is a network of the national standards institutes of 148 countries, on the basis
of one member per country, with a Central Secretariat in Geneva, Switzerland, that
coordinates the system. ISO officially began operations on February 23, 1947.
</t>
</section>
<section anchor="ituorg" title="ITU - International Telecommunication Union">
<t>
http://www.itu.int/
</t>
<t>
The ITU is an international organization within the United Nations System headquartered
in Geneva, Switzerland. The ITU is comprised of three sectors:
</t>
<section anchor="itut" title="ITU Telecommunication Standardization Sector - ITU-T">
<t>
http://www.itu.int/ITU-T/
</t>
<t>
ITU-T's mission is to ensure an efficient and on-time production of high quality
standards covering all fields of telecommunications.
</t>
</section>
<section anchor="itur" title="ITU Radiocommunication Sector - ITU-R">
<t>
http://www.itu.int/ITU-R/
</t>
<t>
The ITU-R plays a vital role in the management of the radio-frequency spectrum
and satellite orbits.
</t>
</section>
<section anchor="itud" title="ITU Telecom Development - ITU-D">
<t>
(also referred as ITU Telecommunication Development Bureau - BDT)
</t>
<t>
http://www.itu.int/ITU-D/
</t>
<t>
The Telecommunication Development Bureau (BDT) is the executive arm of the
Telecommunication Development Sector. Its duties and responsibilities cover
a variety of functions ranging from programme supervision and technical
advice to the collection, processing and publication of information relevant
to telecommunication development.
</t>
</section>
</section>
<section anchor="oasis" title="OASIS - Organization for the Advancement of Structured
Information Standards">
<t>
http://www.oasis-open.org/
</t>
<t>
OASIS is a not-for-profit, international consortium that drives the
development, convergence, and adoption of e-business standards.
</t>
</section>
<section anchor="oif" title="OIF - Optical Internetworking Forum">
<t>
http://www.oiforum.com/
</t>
<t>
On April 20, 1998 Cisco Systems and Ciena Corporation announced an industry-wide
initiative to create the Optical Internetworking Forum, an open forum focused on
accelerating the deployment of optical internetworks.
</t>
</section>
<section anchor="nric" title="NRIC - The Network Reliability and Interoperability Council">
<t>
http://www.nric.org/
</t>
<t>
The purposes of the Committee are to give telecommunications industry leaders the
opportunity to provide recommendations to the FCC and to the industry that assure
optimal reliability and interoperability of telecommunications networks. The
Committee addresses topics in the area of Homeland Security, reliability,
interoperability, and broadband deployment.
</t>
</section>
<section anchor="nstac" title="National Security Telecommunications Advisory Committee (NSTAC)">
<t>
http://www.ncs.gov/nstac/nstac.html
</t>
<t>
President Ronald Reagan created the National Security Telecommunications Advisory
Committee (NSTAC) by Executive Order 12382 in September 1982. Since then, the NSTAC
has served four presidents. Composed of up to 30 industry chief executives representing
the major communications and network service providers and information technology,
finance, and aerospace companies, the NSTAC provides industry-based advice and
expertise to the President on issues and problems related to implementing national
security and emergency preparedness (NS/EP) communications policy. Since its inception,
the NSTAC has addressed a wide range of policy and technical issues regarding
communications, information systems, information assurance, critical infrastructure
protection, and other NS/EP communications concerns.
</t>
</section>
<section anchor="tia" title="TIA - The Telecommunications Industry Association">
<t>
http://www.tiaonline.org/
</t>
<t>
TIA is accredited by ANSI to develop voluntary industry standards for a wide variety
of telecommunications products. TIA's Standards and Technology Department is composed
of five divisions: Fiber Optics, User Premises Equipment, Network Equipment, Wireless
Communications and Satellite Communications.
</t>
</section>
<section anchor="tta" title="TTA - Telecommunications Technology Association">
<t>
http://www.tta.or.kr/Home2003/main/index.jsp
http://www.tta.or.kr/English/new/main/index.htm (English)
</t>
<t>
TTA (Telecommunications Technology Association) is a IT standards organization that develops new standards and provides one-stop services for the establishment of IT standards as well as providing testing and certification for IT products.
</t>
</section>
<section anchor="w3c" title="The World Wide Web Consortium">
<t>
http://www.w3.org/Consortium/
</t>
<t>
The World Wide Web Consortium (W3C) is an international consortium where Member organizations, a full-time staff, and the public work together to develop Web standards. W3C's mission is:
To lead the World Wide Web to its full potential by developing protocols and guidelines that ensure long-term growth for the Web.
</t>
<t>
The security work within the W3C
</t>
<t>
http://www.w3.org/Security/Activity
</t>
</section>
<section anchor="ws-i" title="Web Services Interoperability Organization (WS-I)">
<t>
http://www.ws-i.org/
</t>
<t>
WS-I is an open, industry organization chartered to promote Web services
interoperability across platforms, operating systems, and programming
languages. The organization works across the industry and standards
organizations to respond to customer needs by providing guidance, best
practices, and resources for developing Web services solutions.
</t>
</section>
</section>
<section anchor="docs" title="Security Best Practices Efforts and Documents">
<t>
This section lists the works produced by the SDOs.
</t>
<section anchor="3gppSA3" title="3GPP - TSG SA WG3 (Security)">
<t>
http://www.3gpp.org/TB/SA/SA3/SA3.htm
</t>
<t>
TSG SA WG3 Security is responsible for the security of the 3GPP system,
performing analyses of potential security threats to the system, considering
the new threats introduced by the IP based services and systems and setting
the security requirements for the overall 3GPP system.
</t>
<t>
Specifications: http://www.3gpp.org/ftp/Specs/html-info/TSG-WG--S3.htm
</t>
<t>
Work Items: http://www.3gpp.org/ftp/Specs/html-info/TSG-WG--s3--wis.htm
</t>
<t>
3GPP Confidentiality and Integrity algorithms:
http://www.3gpp.org/TB/Other/algorithms.htm
</t>
</section>
<section anchor="3gpp2TSGS" title="3GPP2 - TSG-S Working Group 4 (Security)">
<t>
http://www.3gpp2.org/Public_html/S/index.cfm
</t>
<t>
The Services and Systems Aspects TSG (TSG-S) is responsible for the
development of service capability requirements for systems based on 3GPP2
specifications. Among its responsibilities TSG-S is addressing management,
technical coordination, as well as architectural and requirements development
associated with all end-to-end features, services and system capabilities
including, but not limited to, security and QoS.
</t>
<t>
TSG-S Specifications: http://www.3gpp2.org/Public_html/specs/index.cfm#tsgs
</t>
</section>
<section anchor="t1.276" title="American National Standard T1.276-2003 - Baseline Security Requirements for the Management Plane">
<t>
Abstract: This standard contains a set of baseline security requirements for the
management plane. The President's National Security Telecommunications Advisory
Committee Network Security Information Exchange (NSIE) and Government NSIE jointly
established a Security Requirements Working Group (SRWG) to examine the security
requirements for controlling access to the public switched network, in particular
with respect to the emerging next generation network. In the telecommunications
industry, this access incorporates operation, administration, maintenance, and
provisioning for network elements and various supporting systems and databases.
Members of the SRWG, from a cross-section of telecommunications carriers and
vendors, developed an initial list of security requirements that would allow
vendors, government departments and agencies, and service providers to implement
a secure telecommunications network management infrastructure. This initial list
of security requirements was submitted as a contribution to Committee
T1 - Telecommunications, Working Group T1M1.5 for consideration as a standard.
The requirements outlined in this document will allow vendors, government
departments and agencies, and service providers to implement a secure
telecommunications network management infrastructure.
</t>
<t>
Documents: http://webstore.ansi.org/ansidocstore/product.asp?sku=T1%2E276%2D2003
</t>
</section>
<section anchor="dmtfSPAM" title="DMTF - Security Protection and Management (SPAM)
Working Group">
<t>
http://www.dmtf.org/about/committees/spamWGCharter.pdf
</t>
<t>
The Working Group will define a CIM Common Model that addresses security
protection and detection technologies, which may include devices and services,
and classifies security information, attacks, and responses.
</t>
</section>
<section anchor="dmtfUser" title="DMTF - User and Security Working Group">
<t>
http://www.dmtf.org/about/committees/userWGCharter.pdf
</t>
<t>
The User and Security Working Group defines objects and access methods
required for principals - where principals include users, groups, software
agents, systems, and organizations.
</t>
</section>
<section anchor="TOPSworkplan" title="ATIS Work-Plan to Achieve Interoperable,
Implementable, End-To-End Standards and Solutions">
<t>
ftp://ftp.t1.org/T1M1/NEW-T1M1.0/3M101940.pdf
</t>
<t>
The ATIS TOPS Security Focus Group has made
recommendations on work items needed to be performed by other SDOs.
</t>
<section anchor="atisfilter" title="ATIS Work on Packet Filtering">
<t>
A part of the ATIS Work Plan was to define how disruptions may be
prevented by filtering unwanted traffic at the edges of the network.
ATIS is developing this work in a document titled, "Traffic Filtering
for the Prevention of Unwanted Traffic".
</t>
</section>
</section>
<section anchor="atisngn" title="ATIS Work on the NGN">
<t>
http://www.atis.org/tops/WebsiteDocuments/NGN/Working%20Docs/Part%20I/ATIS_NGN_Part_1_Issue1.pdf
</t>
<t>
In November 2004, ATIS released Part I of the ATIS NGN-FG efforts entitled,
"ATIS Next Generation Network (NGN) Framework Part I: NGN Definitions, Requirements,
and Architecture, Issue 1.0, November 2004."
</t>
</section>
<section anchor="ccVx" title="Common Criteria">
<t>
http://www.commoncriteriaportal.org/
</t>
<t>
Version 1.0 of the CC was completed in January 1996. Based on a number of trial
evaluations and an extensive public review, Version 1.0 was extensively revised and
CC Version 2.0 was produced in April of 1998. This became ISO International Standard
15408 in 1999. The CC Project subsequently incorporated the minor changes that had
resulted in the ISO process, producing CC version 2.1 in August 1999. Version 3.0
was published in June 2005 and is available for comment.
</t>
<t>
The official version of the Common Criteria and of the Common Evaluation Methodology
is v2.3 which was published in August 2005.
</t>
<t>
All Common Criteria publications contain:
<list>
<t>
Part 1: Introduction and general model
</t><t>
Part 2: Security functional components
</t><t>
Part 3: Security assurance components
</t>
</list>
</t>
<t>
Documents: Common Criteria V2.3 http://www.commoncriteriaportal.org/public/expert/index.php?menu=2
</t>
</section>
<section anchor="etsigsc" title="ETSI">
<t>
http://www.etsi.org/
</t>
<t>
The ETSI hosted the ETSI Global Security Conference in late November, 2003, which
could lead to a standard.
</t>
<t>
Groups related to security located from the ETSI Groups Portal:
<list>
<t>
OCG Security
</t>
<t>
3GPP SA3
</t>
<t>
TISPAN WG7
</t>
</list>
</t>
</section>
<section anchor="ggfSEC" title="GGF Security Area (SEC)">
<t>
https://forge.gridforum.org/projects/sec/
</t>
<t>
The Security Area (SEC) is concerned with various issues relating to
authentication and authorization in Grid environments.
</t>
<t>Working groups:
</t>
<list>
<t>
Authorization Frameworks and Mechanisms WG (AuthZ-WG) -
https://forge.gridforum.org/projects/authz-wg
</t>
<t>
Certificate Authority Operations Working Group (CAOPS-WG) -
https://forge.gridforum.org/projects/caops-wg
</t>
<t>
OGSA Authorization Working Group (OGSA-AUTHZ) -
https://forge.gridforum.org/projects/ogsa-authz
</t>
<t>
Grid Security Infrastructure (GSI-WG) -
https://forge.gridforum.org/projects/gsi-wg
</t>
</list>
</section>
<section anchor="ieeeia" title="Information System Security Assurance Architecture">
<t>
IEEE Working Group - http://issaa.org/
</t>
<t>
Formerly the Security Certification and Accreditation of Information Systems (SCAISWG),
IEEE Project 1700's purpose is to develop a draft Standard for Information System
Security Assurance Architecture for ballot and during the process begin development of a
suite of associated standards for components of that architecture.
</t>
<t>
Documents: http://issaa.org/documents/index.html
</t>
</section>
<section anchor="jones" title="Operational Security Requirements for IP Network Infrastructure :
Advanced Requirements">
<t>
IETF RFC 3871
</t>
<t>
Abstract: This document defines a list of operational security requirements
for the infrastructure of large ISP IP networks (routers and switches). A
framework is defined for specifying "profiles", which are collections of
requirements applicable to certain network topology contexts (all, core-only,
edge-only...). The goal is to provide network operators a clear, concise way
of communicating their security requirements to vendors.
</t>
<t>
Documents:
<list>
<t>
ftp://ftp.rfc-editor.org/in-notes/rfc3871.txt
</t>
</list>
</t>
</section>
<section anchor="incitscs1" title="INCITS CS1 - Cyber Security">
<t>
http://cs1.incits.org/
</t>
<t>
INCITS/CS1 was established in April 2005 to serve as the US TAG for ISO/IEC JTC 1/SC 27
and all SC 27 Working Groups except WG 2 (INCITS/T4 serves as the US TAG to SC 27/WG 2).
</t>
<t>
The scope of CS1 explicitly excludes the areas of work on cyber security standardization
presently underway in INCITS B10, M1 and T3; as well as other standard groups, such as
ATIS, IEEE, IETF, TIA, and X9. INCITS T4's area of work would be narrowed to cryptography
projects in ISO/IEC JTC 1/SC 27 WG 2 (Security techniques and mechanisms).
</t>
</section>
<section anchor="isomgmt" title="ISO Guidelines for the Management of IT Security -
GMITS">
<t>
Guidelines for the Management of IT Security -- Part 1: Concepts and models
for IT Security
</t>
<t>
http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=21733&ICS1=35
</t>
<t>
Guidelines for the Management of IT Security -- Part 2: Managing and planning
IT Security
</t>
<t>
http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=21755&ICS1=35&ICS2=40&ICS3=
</t>
<t>
Guidelines for the Management of IT Security -- Part 3: Techniques for the
management of IT Security
</t>
<t>
http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=21756&ICS1=35&ICS2=40&ICS3=
</t>
<t>
Guidelines for the Management of IT Security -- Part 4: Selection of
safeguards
</t>
<t>
http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=29240&ICS1=35&ICS2=40&ICS3=
</t>
<t>
Guidelines for the Management of IT Security - Part 5: Management guidance on
network security
</t>
<t>
http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=31142&ICS1=35&ICS2=40&ICS3=
</t>
<t>
Open Systems Interconnection -- Network layer security protocol
</t>
<t>
http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=22084&ICS1=35&ICS2=100&ICS3=30
</t>
</section>
<section anchor="isoSC27" title="ISO JTC 1/SC 27">
<t>
http://www.iso.ch/iso/en/stdsdevelopment/techprog/workprog/TechnicalProgrammeSCDetailPage.TechnicalProgrammeSCDetail?COMMID=143
</t>
<t>
Several security related ISO projects under JTC 1/SC 27 are listed here
such as:
<list>
<t>
IT security techniques -- Entity authentication
</t>
<t>
Security techniques -- Key management
</t>
<t>
Security techniques -- Evaluation criteria for IT security
</t>
<t>
Security techniques -- A framework for IT security assurance
</t>
<t>
IT Security techniques -- Code of practice for information security
management
</t>
<t>
Security techniques -- IT network security
</t>
<t>
Guidelines for the implementation, operation and management of
Intrusion Detection Systems (IDS)
</t>
<t>
International Security, Trust, and Privacy Alliance -- Privacy
Framework
</t>
</list>
</t>
</section>
<section anchor="itutsg2" title="ITU-T Study Group 2">
<t>
http://www.itu.int/ITU-T/studygroups/com02/index.asp
</t>
<t>
Security related recommendations currently under study:
<list>
<t>
E.408 Telecommunication networks security requirements Q.5/2 (was E.sec1)
</t>
<t>
E.409 Incident Organisation and Security Incident Handling Q.5/2 (was E.sec2)
</t>
</list>
</t>
<t>
Note: Access requires TIES account.
</t>
</section>
<section anchor="itutm3016" title="ITU-T Recommendation M.3016">
<t>
http://www.itu.int/itudoc/itu-t/com4/contr/068.html
</t>
<t>
This recommendation provides an overview and framework that identifies the
security requirements of a TMN and outlines how available security services
and mechanisms can be
applied within the context of the TMN functional architecture.
</t>
<t>
Question 18 of Study Group 3 is revising Recommendation M.3016. They have taken
the original document and are incorporating thoughts from ITU-T Recommendation
X.805 and from ANSI T1.276-2003. The group has produced a new series of documents.
</t>
<list>
<t>
M.3016.0 - Overview
</t>
<t>
M.3016.1 - Requirements
</t>
<t>
M.3016.2 - Services
</t>
<t>
M.3016.3 - Mechanisms
</t>
<t>
M.3016.4 - Profiles
</t>
</list>
</section>
<section anchor="itutx805" title="ITU-T Recommendation X.805">
<t>
http://www.itu.int/itudoc/itu-t/aap/sg17aap/history/x805/x805.html
</t>
<t>
This Recommendation defines the general security-related architectural
elements that, when appropriately applied, can provide end-to-end network
security.
</t>
</section>
<section anchor="itutsg16" title="ITU-T Study Group 16">
<t>
http://www.itu.int/ITU-T/studygroups/com16/index.asp
</t>
<t>
Multimedia Security in Next-Generation Networks (NGN-MM-SEC)
</t>
<t>
http://www.itu.int/ITU-T/studygroups/com16/sg16-q25.html
</t>
</section>
<section anchor="itutsg17" title="ITU-T Study Group 17">
<t>
http://www.itu.int/ITU-T/studygroups/com17/index.asp
</t>
<t>
ITU-T Study Group 17 is the Lead Study Group on Communication System Security
</t>
<t>
http://www.itu.int/ITU-T/studygroups/com17/cssecurity.html
</t>
<t>
Study Group 17 Security Project:
</t>
<t>
http://www.itu.int/ITU-T/studygroups/com17/security/index.html
</t>
<t>
During its November 2002 meeting, Study Group 17 agreed to establish a
new project entitled "Security Project" under the leadership of Q.10/17 to
coordinate the ITU-T standardization effort on security. An analysis of
the status on ITU-T Study Group action on information and communication
network security may be found in TSB Circular 147 of 14 February 2003.
</t>
</section>
<section anchor="itutrec" title="Catalogue of ITU-T Recommendations related to Communications System Security">
<t>
http://www.itu.int/itudoc/itu-t/com17/activity/cat004.html
</t>
<t>
The Catalogue of the approved security Recommendations include those, designed
for security purposes and those, which describe or use of functions of security
interest and need. Although some of the security related Recommendations
includes the phrase "Open Systems Interconnection", much of the information
contained in them is pertinent to the establishment of security functionality
in any communicating system.
</t>
</section>
<section anchor="itutsecman" title="ITU-T Security Manual">
<t>
http://www.itu.int/ITU-T/edh/files/security-manual.pdf
</t>
<t>
TSB is preparing an "ITU-T Security Manual" to provide an overview on security
in telecommunications and information technologies, describe practical issues,
and indicate how the different aspects of security in today's applications are
addressed by ITU-T Recommendations. This manual has a tutorial character: it
collects security related material from ITU-T Recommendations into one place
and explains the respective relationships. The intended audience for this
manual are engineers and product managers, students and academia, as well as
regulators who want to better understand security aspects in practical
applications.
</t>
</section>
<section anchor="itungn" title="ITU-T NGN Effort">
<t>
http://www.itu.int/ITU-T/2001-2004/com13/ngn2004/index.html
</t>
<t>
During its January 2002 meeting, SG13 decided to undertake the preparation of a new
ITU-T Project entitled "NGN 2004 Project". At the November 2002 SG13 meeting, a
preliminary description of the Project was achieved and endorsed by SG13 with the
goal to launch the Project. It is regularly updated since then.
</t>
<t>
The role of the NGN 2004 Project is to organize and to coordinate ITU-T activities
on Next Generation Networks. Its target is to produce a first set of Recommendations
on NGN by the end of this study period, i.e. mid-2004.
</t>
</section>
<section anchor="nricVrec" title="NRIC VI Focus Groups">
<t>
http://www.nric.org/fg/index.html
</t>
<t>
The Network Reliability and Interoperability Council (NRIC) was formed with
the purpose to provide recommendations to the FCC and to the industry to assure
the reliability and interoperability of wireless, wireline, satellite, and cable
public telecommunications networks. These documents provide general information
and guidance on NRIC Focus Group 1B (Cybersecurity) Best Practices for the
prevention of cyberattack and for restoration following a cyberattack.
</t>
<t>
Documents:
<list>
<t>
Homeland Defense - Recommendations Published 14-Mar-03
</t>
<t>
Preventative Best Practices - Recommendations Published 14-Mar-03
</t>
<t>
Recovery Best Practices - Recommendations Published 14-Mar-03
</t>
<t>
Best Practice Appendices - Recommendations Published 14-Mar-03
</t>
</list>
</t>
</section>
<section anchor="oasisSecJC" title="OASIS Security Joint Committee">
<t>
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=security-jc
</t>
<t>
The purpose of the Security JC is to coordinate the technical activities of
multiple security related TCs. The SJC is advisory only, and has no
deliverables. The Security JC will promote the use of consistent terms,
promote re-use, champion an OASIS security standards model, provide consistent
PR, and promote mutuality, operational independence and ethics.
</t>
</section>
<section anchor="oasisSecTC" title="OASIS Security Services (SAML) TC">
<t>
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=security
</t>
<t>
The Security Services TC is working to advance the Security Assertion Markup
Language (SAML) as an OASIS standard. SAML is an XML framework for exchanging
authentication and authorization information.
</t>
</section>
<section anchor="oifia" title="OIF Implementation Agreements">
<t>
The OIF has 2 approved Implementation Agreements (IAs) relating to security.
They are:
</t>
<t>
OIF-SMI-01.0 - Security Management Interfaces to Network Elements
</t>
<t>
This Implementation Agreement lists objectives for securing OAM&P
interfaces to a Network Element and then specifies ways of using security
systems (e.g., IPsec or TLS) for securing these interfaces. It summarizes
how well each of the systems, used as specified, satisfies the objectives.
</t>
<t>
OIF - SEP - 01.1 - Security Extension for UNI and NNI
</t>
<t>
This Implementation Agreement defines a common Security Extension for
securing the protocols used in UNI 1.0, UNI 2.0, and NNI.
</t>
<t>
Documents: http://www.oiforum.com/public/documents/Security-IA.pdf
</t>
</section>
<section anchor="tiaonline" title="TIA">
<t>
The TIA has produced the "Compendium of Emergency Communications and
Communications Network Security-related Work Activities". This document
identifies standards, or other technical documents and ongoing
Emergency/Public Safety Communications and Communications Network
Security-related work activities within TIA and it's Engineering
Committees. Many P25 documents are specifically detailed. This "living
document" is presented for information, coordination and reference.
</t>
<t>
Documents: http://www.tiaonline.org/standards/technology/ciphs/documents/EMTEL_sec.pdf
</t>
</section>
<section anchor="ws-iSecProfile" title="WS-I Basic Security Profile">
<t>
http://www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html
</t>
<t>
The WS-I Basic Security Profile 1.0 consists of a set of non-proprietary
Web services specifications, along with clarifications and amendments to those
specifications which promote interoperability.
</t>
</section>
</section>
<section anchor="sec" title="Security Considerations">
<t>
This document describes efforts to standardize security practices and
documents. As such this document offers no security guidance whatsoever.
</t>
<t>
Readers of this document should be aware of the date of publication of
this document. It is feared that they may assume that the efforts, on-line
material, and documents are current whereas they may not be. Please
consider this when reading this document.
</t>
</section>
<section anchor="iana" title="IANA Considerations">
<t>
This document does not propose a standard and does not require the
IANA to do anything.
</t>
</section>
<section anchor="Acks" title="Acknowledgments">
<t>
The following people have contributed to this document. Listing their names here does
not mean that they endorse the document, but that they have contributed to its
substance.
</t>
<t>
David Black, Mark Ellison, George Jones, Keith McCloghrie, John McDonough, Art Reilly, Chip Sharp,
Dane Skow, Michael Hammer, Bruce Moon.
</t>
</section>
<section anchor="diffs" title="Changes from Prior Drafts">
<t>
-00 : Initial draft published as draft-lonvick-sec-efforts-01.txt
</t>
<t>
-01 : Security Glossaries:
<list><t>
<list><t>
Added ATIS Telecom Glossary 2000, Critical Infrastructure Glossary of Terms and
Acronyms, Microsoft Solutions for Security Glossary, and USC InfoSec Glossary.
</t></list>
</t>
<t>
Standards Developing Organizations:
</t>
<list><t>
Added DMTF, GGF, INCITS, OASIS, and WS-I
</t>
<t>
Removal of Committee T1 and modifications to ATIS and former T1 technical
subcommittees due to the recent ATIS reorganization.
</t></list>
<t>
Efforts and Documents:
</t>
<list><t>
Added DMTF User and Security WG, DMTF SPAM WG, GGF Security Area (SEC), INCITS
Technical Committee T4 - Security Techniques, INCITS Technical Committee T11 -
Fibre Channel Interfaces, ISO JTC 1/SC 27 projects, OASIS Security Joint Committee,
OASIS Security Services TC, and WS-I Basic Security Profile.
</t>
<t>
Updated Operational Security Requirements for IP Network Infrastructure : Advanced
Requirements.
</t></list>
</list>
</t>
<t>
-00 : as the WG ID
<list><t>
Added more information about the ITU-T SG3 Q18 effort to modify ITU-T Recommendation M.3016.
</t></list>
</t>
<t>
-01 : First revision as the WG ID.
<list><t>
Added information about the NGN in the sections about ATIS, the NSTAC, and ITU-T.
</t></list>
</t>
<t>
-02 : Second revision as the WG ID.
<list><t>
Updated the date.</t>
<t>
Corrected some url's and the reference to George's RFC.
</t></list>
</t>
<t>
-03 : Third revision of the WG ID.
<list><t>
Updated the date.</t>
<t>
Updated the information about the CC</t>
<t>
Added a Conventions section (not sure how this document got to where it is without that)
</t></list>
</t>
<t>
-04 : Fourth revision of the WG ID.
<list>
<t>
Updated the date.
</t>
<t>
Added Anne & Lynn Wheeler Taxonomy & Security Glossary
</t>
<t>
CIAO glossary removed. CIAO has been absorbed by DHS and the glossary is no longer available.
</t>
<t>
USC glossary removed, could not find it on the site or a reference to it elsewhere.
</t>
<t>
Added TTA - Telecommunications Technology Association to SDO section.
</t>
<t>
Removed ATIS Security & Emergency Preparedness Activities from Documents section. Could not find it or a reference to it.
</t>
<t>
INCITS T4 incorporated into CS1 - T4 section removed
</t>
<t>
X9 Added to SDO list under ANSI
</t>
<t>
Various link or grammar fixes.
</t>
</list>
</t>
<t>
-05 : Fifth revision of the WG ID.
<list>
<t>
Updated the date.
</t>
<t>
Removed the 2119 definitions; this is an informational document.
</t>
</list>
</t>
<t>
-06 : Sixth revision of the WG ID.
<list>
<t>
Updated the date.
</t>
<t>
Added W3C information.
</t>
</list>
</t>
<t>
-07 : Seventh revision of the WG ID.
<list>
<t>
Updated the date.
</t>
</list>
</t>
<t>
-08 : Eighth revision of the WG ID.
<list>
<t>
Updated the reference to RFC 4949, found by Stephen Kent.
</t>
</list>
</t>
<t>
-09 : Nineth revision of the WG ID.
<list>
<t>
Updated the date.
</t>
</list>
</t>
<t>
Note: This section will be removed before publication as an RFC.
</t>
</section>
</middle>
<back>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 10:54:20 |