Date Published: March 2007
Author(s)
Shirley Radack (NIST)
This bulletin summarizes the recommendations developed by NIST to assist organizations in designing, implementing and operating email systems that are secure. Topics covered in the bulletin include a description of the contents and the appendices of the guideline; the structure of email systems; and the use of cryptography to protect the confidentiality and integrity of email. NIST?s recommendations to organizations on planning and managing mail servers, securing the operating system, securing the mail client, using network protection mechanisms, and maintaining security are summarized.
This bulletin summarizes the recommendations developed by NIST to assist organizations in designing, implementing and operating email systems that are secure. Topics covered in the bulletin include a description of the contents and the appendices of the guideline; the structure of email systems; and...
See full abstract
This bulletin summarizes the recommendations developed by NIST to assist organizations in designing, implementing and operating email systems that are secure. Topics covered in the bulletin include a description of the contents and the appendices of the guideline; the structure of email systems; and the use of cryptography to protect the confidentiality and integrity of email. NIST?s recommendations to organizations on planning and managing mail servers, securing the operating system, securing the mail client, using network protection mechanisms, and maintaining security are summarized.
Hide full abstract
Keywords
cyptography; electronic mail systems; email security; information security; information system standards; mail clients; mail servers; network security; operating system
Control Families
Access Control; Audit and Accountability; Configuration Management; Contingency Planning; Identification and Authentication; Planning; Risk Assessment; System and Communications Protection; System and Information Integrity
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
