Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 21.7

Cryptographic Message Syntax (CMS)
Cryptographic Message Syntax (CMS) Standard or Specification

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: The Cryptographic Message Syntax (CMS) standard is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. The CMS describes encapsulation syntax for data protection. It supports digital signatures and encryption. The syntax allows multiple encapsulations; this means one encapsulation envelope can be nested inside another. It also allows arbitrary attributes, such as signing time, to be signed along with the message content, and it provides for other attributes such as countersignatures to be associated with a signature.
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v20.4
Decision Date: 04/23/2020
Aliases: RFC 3852, RFC 5652
Introduced By:
Standards Body: Internet Engineering Task Force (IETF)
- The information contained on this page is accurate as of the Decision Date (04/23/2020).