Guide to Writing Security Capability Profiles
draft-jones-opsec-profile-guide-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | George M. Jones | ||
| Last updated | 2006-08-29 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document provides guidelines for creating security capability profiles. A profile is a list of features that are required to operate a device in a a secure manner in a specific environment. It is anticipated that what is required in a profile will vary over time and, across different classes of devices (e.g. a network edge device may need to filter customer traffic whereas core network devices may not), and in different organizations. This document does not define a profile or specify requirements, but rather gives guidance for their creation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)