All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David O'Brien" <daobrien@redhat.com>
To: selinux@tycho.nsa.gov, fedora-selinux-list@redhat.com,
	rhselinux-project@redhat.com
Subject: RHEL5 Security Documentation Scope Statement
Date: Fri, 14 Jul 2006 16:31:42 +1000	[thread overview]
Message-ID: <200607141631.42793.daobrien@redhat.com> (raw)

I've prepared the following Scope Statement to help those involved in the 
project to update the RHEL5 Security Documentation. Please feel free to offer 
any suggestions, ask questions or get clarification. As we move forward there 
may be minor changes, but this should be pretty close.

Apologies for the cross-post and to those who receive multiple copies. Please 
forward this to interested parties who may not be on any of these lists.

----
The RHEL5 Security Guide integrates two previously separate guides: The Red 
Hat Enterprise Linux 4 Security Guide and the Red Hat Enterprise Linux 4 
SELinux Guide. These guides are being integrated and updated to provide a 
single source of information for all security-related topics for Red Hat 
Enterprise Linux.
 
The RHEL5 Security Guide provides a general introduction to security, and from 
the perspective of Red Hat Linux in particular. It provides conceptual 
information in the areas of security assessment, common exploits, and 
intrusion and incident response. It also provides conceptual and specific 
configuration information for hardening Workstation, Server, VPN, firewall 
and other implementations using SELinux. A Troubleshooting section provides 
information on common problems and how to resolve them.
 
The RHEL5 Security Guide assumes a basic knowledge of IT security, and 
consequently provides only minimal coverage of common security practices such 
as controlling physical access, sound account-keeping policies and 
procedures, auditing, etc. Neither does it cover the intricacies of SELinux 
in detail, such as writing policies for certain 3rd party applications. Where 
appropriate, reference is made to external resources for this and related 
information.

----
regards, 
David O'Brien
Red Hat Asia Pacific Pty Ltd

Tel:  +61-7-3514-8189
Fax: +61-7-3514-8199

email: daobrien@redhat.com
web: http://apac.redhat.com/

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

                 reply	other threads:[~2006-07-14  6:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200607141631.42793.daobrien@redhat.com \
    --to=daobrien@redhat.com \
    --cc=fedora-selinux-list@redhat.com \
    --cc=rhselinux-project@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.