emasser 3.4.1 → 3.12.0

data/lib/emasser/help/approvalCac_post_mapper.md

@@ -1,20 +1,20 @@
-Submit control to second role of CAC
-
-Endpoint request parameters/fields
-
-Field             Data Type  Details
--------------------------------------------------------------------------------------------------
-systemId          Integer    [Required] Unique system identifier 
-controlAcronym    String     [Required] Control acronym associated with the POA&M Item. NIST SP 800-53 Revision 4 defined.
-complianceStatus  String     [Read-Only] Compliance status of the control.
-currentStageName  String     [Read-Only] Current role.
-currentStage      Integer    [Read-Only] Current step in the Control Approval Chain.
-totalStages       Integer    [Read-Only] Total number of steps in Control Approval Chain.
-comments*         String     [Conditional] Comments related to package approval chain. 10,000 Characters.
-
-*Comments are not a required field at the first role of the CAC but are required at the second
-role of the CAC. Comments cannot exceed 10,000 characters.
-
-Example:
-
-bundle exec exe/emasser post cac add --systemId [value] --controlAcronym [value] --comments [value]
+Submit control to second role of CAC
+
+Endpoint request parameters/fields
+
+Field             Data Type  Details
+-------------------------------------------------------------------------------------------------
+systemId          Integer    [Required] Unique system identifier 
+controlAcronym    String     [Required] Control acronym associated with the POA&M Item. NIST SP 800-53 Revision 4 defined.
+complianceStatus  String     [Read-Only] Compliance status of the control.
+currentStageName  String     [Read-Only] Current role.
+currentStage      Integer    [Read-Only] Current step in the Control Approval Chain.
+totalStages       Integer    [Read-Only] Total number of steps in Control Approval Chain.
+comments*         String     [Conditional] Comments related to package approval chain. 10,000 Characters.
+
+*Comments are not a required field at the first role of the CAC but are required at the second
+role of the CAC. Comments cannot exceed 10,000 characters.
+
+Example:
+
+bundle exec exe/emasser post cac add --systemId [value] --controlAcronym [value] --comments [value]

data/lib/emasser/help/approvalPac_post_mapper.md

@@ -1,20 +1,20 @@
-Submit system package for review
-
-Endpoint request parameters/fields
-
-Field         Data Type  Details
--------------------------------------------------------------------------------------------------
-systemId      Integer    [Required] Unique system identifier 
-workflow      String     [Required] Values include the following: (Assess and Authorize
-                                    Assess Only, Security Plan Approval)
-name          String     [Required] Package name. 100 Characters.
-comments      String     [Required] Comments related to package approval chain. 4000 Characters.
-
-currentRole   String     [Read-Only] Current role in active package.
-currentStep   Integer    [Read-Only] Current step in the package Approval Chain.
-totalSteps    Integer    [Read-Only] Total number of steps in Package Approval Chain.
-
-
-Example:
-
-bundle exec exe/emasser post pac add --systemId [value] --workflow [value] --name [value] --comments [value]
+Submit system package for review
+
+Endpoint request parameters/fields
+
+Field         Data Type  Details
+-------------------------------------------------------------------------------------------------
+systemId      Integer    [Required] Unique system identifier 
+workflow      String     [Required] Values include the following: (Assess and Authorize
+                                    Assess Only, Security Plan Approval)
+name          String     [Required] Package name. 100 Characters.
+comments      String     [Required] Comments related to package approval chain. 4000 Characters.
+
+currentRole   String     [Read-Only] Current role in active package.
+currentStep   Integer    [Read-Only] Current step in the package Approval Chain.
+totalSteps    Integer    [Read-Only] Total number of steps in Package Approval Chain.
+
+
+Example:
+
+bundle exec exe/emasser post pac add --systemId [value] --workflow [value] --name [value] --comments [value]

data/lib/emasser/help/artifacts_del_mapper.md

@@ -1,9 +1,9 @@
-Remove one or many artifacts in a system
-
-Provide single file or a space/comma delimited list of file names to be removed from the system (systemId)
-
-Example:
-
-bundle exec exe/emasser delete artifacts remove --systemId [value] --files [value] 
-or
-bundle exec exe/emasser delete artifacts remove --systemId [value] --files [value ... value] 
+Remove one or many artifacts in a system
+
+Provide single file or a space/comma delimited list of file names to be removed from the system (systemId)
+
+Example:
+
+bundle exec exe/emasser delete artifacts remove -s, --systemId [value] -f, --files [value] 
+or
+bundle exec exe/emasser delete artifacts remove -s, --systemId [value] -f, --files [value ... value] 

data/lib/emasser/help/artifacts_post_mapper.md

@@ -1,59 +1,59 @@
-Endpoint request parameters/fields
-
-Field                   Data Type  Details
--------------------------------------------------------------------------------------------------
-systemId                Integer    [Required] Unique eMASS identifier. Will need to provide correct number.
-isTemplate              Boolean    [Required] Indicates whether an artifact is a template.
-type*                   String     [Required] Values include the following: (Procedure, Diagram, Policy, Labor,
-                                              Document, Image, Other, Scan Result, Auditor Report)
-category*               String     [Required] Values include the following: (Implementation Guidance, Evidence)
-files                   String     [Required] File names (to include path) to be uploaded into eMASS as artifacts
-
-description             String     [Optional] Artifact description. 2000 Characters.
-refPageNumber           String     [Optional] Artifact reference page number. 50 Characters.
-ccis                    String     [Optional] CCIs associated with artifact.
-controls                String     [Optional] Control acronym associated with the artifact. NIST SP 800-53 Revision 4 defined.
-artifactExpirationDate  Date       [Optional] Date Artifact expires and requires review. In Unix Date Format
-lastReviewedDate        Date       [Optional] Date Artifact was last reviewed. In Unix Date Format
-
-isInherited             Boolean    [Read-Only] Indicates whether an artifact is inherited.
-mimeContentType         String     [Read-Only] Standard MIME content type derived from file extension.
-fileSize                String     [Read-Only] File size of attached artifact.
-
-* May also accept custom artifact type or category values set by system administrators.
-
-The request body of a POST request through the Artifact Endpoint accepts a single binary file with file extension.zip only.
-
-This accepted .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt.
-
-Filename uniqueness throughout eMASS will be enforced by the API.
-
-Upon successful receipt of a file, if a file within the .zip is matched via filename to an artifact existing within the application, the file associated with the artifact will be updated.
-
-If no artifact is matched via filename to the application, a new artifact will be created with the following default values. Any values not specified below will be blank.
-  - isTemplate: false
-  - type: other
-  - category: evidence
-
-To update values other than the file itself, please submit a PUT request.
-
-Business Rules
-- Artifact cannot be saved if the file does not have the following file extensions:
-  - .docx,.doc,.txt,.rtf,.xfdl,.xml,.mht,.mhtml,.html,.htm,.pdf
-  - .mdb,.accdb,.ppt,.pptx,.xls,.xlsx,.csv,.log
-  - .jpeg,.jpg,.tiff,.bmp,.tif,.png,.gif
-  - .zip,.rar,.msg,.vsd,.vsw,.vdx, .z{#}, .ckl,.avi,.vsdx
-- Artifact cannot be saved if File Name (fileName) exceeds 1,000 characters
-- Artifact cannot be saved if Description (description) exceeds 2,000 characters
-- Artifact cannot be saved if Reference Page Number (refPageNumber) exceeds 50 characters
-- Artifact cannot be saved if the file does not have an allowable file extension/type.
-- Artifact version cannot be saved if an Artifact with the same file name already exist in the system.
-- Artifact cannot be saved if the file size exceeds 30MB.
-- Artifact cannot be saved if the Last Review Date is set in the future.
-
-
-Example:
-
-bundle exec exe/emasser post artifacts upload --systemId [value] [--isTemplate or --no-isTemplate] --type [value] --category [value] --files[value...value]
-
-Note: The example does not list any optional fields
+Endpoint request parameters/fields
+
+Field                   Data Type  Details
+-------------------------------------------------------------------------------------------------
+systemId                Integer    [Required] Unique eMASS identifier. Will need to provide correct number.
+isTemplate              Boolean    [Required] Indicates whether an artifact is a template.
+type*                   String     [Required] Values include the following: (Procedure, Diagram, Policy, Labor,
+                                              Document, Image, Other, Scan Result, Auditor Report)
+category*               String     [Required] Values include the following: (Implementation Guidance, Evidence)
+files                   String     [Required] File names (to include path) to be uploaded into eMASS as artifacts
+
+description             String     [Optional] Artifact description. 2000 Characters.
+refPageNumber           String     [Optional] Artifact reference page number. 50 Characters.
+ccis                    String     [Optional] CCIs associated with artifact.
+controls                String     [Optional] Control acronym associated with the artifact. NIST SP 800-53 Revision 4 defined.
+artifactExpirationDate  Date       [Optional] Date Artifact expires and requires review. In Unix Date Format
+lastReviewedDate        Date       [Optional] Date Artifact was last reviewed. In Unix Date Format
+
+isInherited             Boolean    [Read-Only] Indicates whether an artifact is inherited.
+mimeContentType         String     [Read-Only] Standard MIME content type derived from file extension.
+fileSize                String     [Read-Only] File size of attached artifact.
+
+* May also accept custom artifact type or category values set by system administrators.
+
+The request body of a POST request through the Artifact Endpoint accepts a single binary file with file extension.zip only.
+
+This accepted .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt.
+
+Filename uniqueness throughout eMASS will be enforced by the API.
+
+Upon successful receipt of a file, if a file within the .zip is matched via filename to an artifact existing within the application, the file associated with the artifact will be updated.
+
+If no artifact is matched via filename to the application, a new artifact will be created with the following default values. Any values not specified below will be blank.
+  - isTemplate: false
+  - type: other
+  - category: evidence
+
+To update values other than the file itself, please submit a PUT request.
+
+Business Rules
+- Artifact cannot be saved if the file does not have the following file extensions:
+  - .docx,.doc,.txt,.rtf,.xfdl,.xml,.mht,.mhtml,.html,.htm,.pdf
+  - .mdb,.accdb,.ppt,.pptx,.xls,.xlsx,.csv,.log
+  - .jpeg,.jpg,.tiff,.bmp,.tif,.png,.gif
+  - .zip,.rar,.msg,.vsd,.vsw,.vdx, .z{#}, .ckl,.avi,.vsdx
+- Artifact cannot be saved if File Name (fileName) exceeds 1,000 characters
+- Artifact cannot be saved if Description (description) exceeds 2,000 characters
+- Artifact cannot be saved if Reference Page Number (refPageNumber) exceeds 50 characters
+- Artifact cannot be saved if the file does not have an allowable file extension/type.
+- Artifact version cannot be saved if an Artifact with the same file name already exist in the system.
+- Artifact cannot be saved if the file size exceeds 30MB.
+- Artifact cannot be saved if the Last Review Date is set in the future.
+
+
+Example:
+
+bundle exec exe/emasser post artifacts upload --systemId [value] [--isTemplate or --no-isTemplate] --type [value] --category [value] --files[value...value]
+
+Note: The example does not list any optional fields

data/lib/emasser/help/artifacts_put_mapper.md

@@ -1,34 +1,34 @@
-Endpoint request parameters/fields
-
-Field                   Data Type  Details
--------------------------------------------------------------------------------------------------
-systemId                Integer    [Required] Unique eMASS identifier. Will need to provide correct number.
-filename                String     [Required] File name should match exactly one file within the provided zip file.
-                        Binary     [Required] Application/zip file. Max 30MB per artifact.
-isTemplate              Boolean    [Required] Indicates whether an artifact is a template.
-type*                   String     [Required] Values include the following: (Procedure, Diagram, Policy, Labor,
-                                              Document, Image, Other, Scan Result, Auditor Report)
-category*               String     [Required] Values include the following: (Implementation Guidance, Evidence)
-
-description             String     [Optional] Artifact description. 2000 Characters.
-refPageNumber           String     [Optional] Artifact reference page number. 50 Characters.
-ccis                    String     [Optional] CCIs associated with artifact.
-controls                String     [Optional] Control acronym associated with the artifact. NIST SP 800-53 Revision 4 defined.
-artifactExpirationDate  Date       [Optional] Date Artifact expires and requires review. In Unix Date Format
-lastReviewedDate        Date       [Optional] Date Artifact was last reviewed. In Unix Date Format
-
-isInherited             Boolean    [Read-Only] Indicates whether an artifact is inherited.
-mimeContentType         String     [Read-Only] Standard MIME content type derived from file extension.
-fileSize                String     [Read-Only] File size of attached artifact.
-
-* May also accept custom artifact category values set by system administrators.
-
-
-Updates one artifact in a system - the API endpoint provide the capability of updating multiple artifacts concurrently, however this CLI only supports updating one Artifact at the time.
-
-The file name provided should match exactly one file within the previously uploaded zip file.
-
-
-Example:
-
-bundle exec exe/emasser put artifacts update --systemId [value] [--isTemplate or --no-isTemplate] --type [value] --category [value] --files[value...value]
+Endpoint request parameters/fields
+
+Field                   Data Type  Details
+-------------------------------------------------------------------------------------------------
+systemId                Integer    [Required] Unique eMASS identifier. Will need to provide correct number.
+filename                String     [Required] File name should match exactly one file within the provided zip file.
+                        Binary     [Required] Application/zip file. Max 30MB per artifact.
+isTemplate              Boolean    [Required] Indicates whether an artifact is a template.
+type*                   String     [Required] Values include the following: (Procedure, Diagram, Policy, Labor,
+                                              Document, Image, Other, Scan Result, Auditor Report)
+category*               String     [Required] Values include the following: (Implementation Guidance, Evidence)
+
+description             String     [Optional] Artifact description. 2000 Characters.
+refPageNumber           String     [Optional] Artifact reference page number. 50 Characters.
+ccis                    String     [Optional] CCIs associated with artifact.
+controls                String     [Optional] Control acronym associated with the artifact. NIST SP 800-53 Revision 4 defined.
+artifactExpirationDate  Date       [Optional] Date Artifact expires and requires review. In Unix Date Format
+lastReviewedDate        Date       [Optional] Date Artifact was last reviewed. In Unix Date Format
+
+isInherited             Boolean    [Read-Only] Indicates whether an artifact is inherited.
+mimeContentType         String     [Read-Only] Standard MIME content type derived from file extension.
+fileSize                String     [Read-Only] File size of attached artifact.
+
+* May also accept custom artifact category values set by system administrators.
+
+
+Updates one artifact in a system - the API endpoint provide the capability of updating multiple artifacts concurrently, however this CLI only supports updating one Artifact at the time.
+
+The file name provided should match exactly one file within the previously uploaded zip file.
+
+
+Example:
+
+bundle exec exe/emasser put artifacts update --systemId [value] [--isTemplate or --no-isTemplate] --type [value] --category [value] --files[value...value]

data/lib/emasser/help/cloudresource_post_mapper.md

@@ -1,62 +1,62 @@
-Add cloud resource and scan results in the assets module for a system
-
-Endpoint request parameters/fields
-
-Field                   Data Type  Details
--------------------------------------------------------------------------------------------------
-systemId                 Integer   [Required] Unique eMASS identifier. Will need to provide correct number.
-provider                 String    [Required] Cloud service provider name.
-resourceId               String    [Required] Unique identifier/resource namespace for policy compliance result.
-resourceName             String    [Required] Friendly name of Cloud resource.
-resourceType             String    [Required] Type of Cloud resource.
-
-initiatedBy              String    [Optional] Email of POC.
-cspAccountId             String    [Optional] System/owner's CSP account ID/number.
-cspRegion                String    [Optional] CSP region of system.
-isBaseline               Boolean   [Optional] True/false flag for providing results as baseline.
-                                              If true, all existing compliance results for the resourceId will be replaced by results in the current call.
-
-tags                     Object    [Optional] Informational tags associated to results for other metadata
-  text                   String    [Optional] Tag metadata information
-
-complianceResults        Object    [Required] Compliance result information
-  cspPolicyDefinitionId    String  [Required] Unique identifier/compliance namespace for CSP/Resource’s
-                                            policy definition/compliance check.
-  policyDefinitionTitle    String  [Required] Friendly policy/compliance check title. Recommend short title
-  isCompliant              Boolean [Required] Compliance status of the policy for the identified cloud resource.
-
-  complianceCheckTimestamp Date    [Optional] Unix date format
-  control                  String  [Optional] Comma separated correlation to Security Control
-                                             (e.g. exact NIST Control acronym).
-  assessmentProcedure      String  [Optional] Comma separated correlation to Assessment Procedure
-                                              (i.e. CCI number for DoD Control Set).
-  complianceReason         String  [Optional] Reason/comments for compliance result
-  policyDeploymentName     String  [Optional] Name of policy deployment
-  policyDeploymentVersion  String  [Optional] Version of policy deployment.
-  severity                 String  [Optional] Values include the following: (Low, Medium, High, Critical)
-
-
-  The following Cloud Resource parameters/fields have the following character limitations:
-- Fields that can not exceed 50 characters:
-  - Policy Deployment Version (`policyDeploymentVersion`)
-- Fields that can not exceed 100 characters:
-  - Assessment Procedure      (`assessmentProcedure`)
-  - Security Control Acronym  (`control`)
-  - CSP Account ID            (`cspAccountId`)
-  - CSP Region                (`cspRegion`)
-  - Email of POC              (`initiatedBy`)
-  - Cloud Service Provider    (`provider`)
-  - Type of Cloud resource    (`resourceType`)
-- Fields that can not exceed 500 characters:
-  - CSP/Resource’s Policy ID  (`cspPolicyDefinitionId`)
-  - Policy Deployment Name    (`policyDeploymentName`)
-  - Policy Compliance ID      (`resourceId`)
-  - Cloud Resource Name       (`resourceName`)
-- Fields that can not exceed 1000 characters:
-  - Reason for Compliance (`complianceReason`)
-- Fields that can not exceed 2000 characters:
-  - Policy Short Title    (`policyDefinitionTitle`)
-
-Example:
-
-bundle exec exe/emasser post cloud_resource add --systemId [value] --provider [value] --resourceId [value] --resourceName [value] --resourceType [value] --cspPolicyDefinitionId [value] --isCompliant or --is-not-Compliant --policyDefinitionTitle [value] --test [value]
+Add cloud resource and scan results in the assets module for a system
+
+Endpoint request parameters/fields
+
+Field                   Data Type  Details
+-------------------------------------------------------------------------------------------------
+systemId                 Integer   [Required] Unique eMASS identifier. Will need to provide correct number.
+provider                 String    [Required] Cloud service provider name.
+resourceId               String    [Required] Unique identifier/resource namespace for policy compliance result.
+resourceName             String    [Required] Friendly name of Cloud resource.
+resourceType             String    [Required] Type of Cloud resource.
+
+initiatedBy              String    [Optional] Email of POC.
+cspAccountId             String    [Optional] System/owner's CSP account ID/number.
+cspRegion                String    [Optional] CSP region of system.
+isBaseline               Boolean   [Optional] True/false flag for providing results as baseline.
+                                              If true, all existing compliance results for the resourceId will be replaced by results in the current call.
+
+tags                     Object    [Optional] Informational tags associated to results for other metadata
+  text                   String    [Optional] Tag metadata information
+
+complianceResults        Object    [Required] Compliance result information
+  cspPolicyDefinitionId    String  [Required] Unique identifier/compliance namespace for CSP/Resource’s
+                                            policy definition/compliance check.
+  policyDefinitionTitle    String  [Required] Friendly policy/compliance check title. Recommend short title
+  isCompliant              Boolean [Required] Compliance status of the policy for the identified cloud resource.
+
+  complianceCheckTimestamp Date    [Optional] Unix date format
+  control                  String  [Optional] Comma separated correlation to Security Control
+                                             (e.g. exact NIST Control acronym).
+  assessmentProcedure      String  [Optional] Comma separated correlation to Assessment Procedure
+                                              (i.e. CCI number for DoD Control Set).
+  complianceReason         String  [Optional] Reason/comments for compliance result
+  policyDeploymentName     String  [Optional] Name of policy deployment
+  policyDeploymentVersion  String  [Optional] Version of policy deployment.
+  severity                 String  [Optional] Values include the following: (Low, Medium, High, Critical)
+
+
+  The following Cloud Resource parameters/fields have the following character limitations:
+- Fields that can not exceed 50 characters:
+  - Policy Deployment Version (`policyDeploymentVersion`)
+- Fields that can not exceed 100 characters:
+  - Assessment Procedure      (`assessmentProcedure`)
+  - Security Control Acronym  (`control`)
+  - CSP Account ID            (`cspAccountId`)
+  - CSP Region                (`cspRegion`)
+  - Email of POC              (`initiatedBy`)
+  - Cloud Service Provider    (`provider`)
+  - Type of Cloud resource    (`resourceType`)
+- Fields that can not exceed 500 characters:
+  - CSP/Resource’s Policy ID  (`cspPolicyDefinitionId`)
+  - Policy Deployment Name    (`policyDeploymentName`)
+  - Policy Compliance ID      (`resourceId`)
+  - Cloud Resource Name       (`resourceName`)
+- Fields that can not exceed 1000 characters:
+  - Reason for Compliance (`complianceReason`)
+- Fields that can not exceed 2000 characters:
+  - Policy Short Title    (`policyDefinitionTitle`)
+
+Example:
+
+bundle exec exe/emasser post cloud_resource add --systemId [value] --provider [value] --resourceId [value] --resourceName [value] --resourceType [value] --cspPolicyDefinitionId [value] --isCompliant or --is-not-Compliant --policyDefinitionTitle [value] --test [value]

data/lib/emasser/help/cmmc_get_mapper.md

@@ -1,4 +1,4 @@
-The Cybersecurity Maturity Model Certification (CMMC) Assessments endpoint provides
-the ability to view CMMC assessment information. 
-
-**It is available to CMMC eMASS only.**
+The Cybersecurity Maturity Model Certification (CMMC) Assessments endpoint provides
+the ability to view CMMC assessment information. 
+
+**It is available to CMMC eMASS only.**

data/lib/emasser/help/container_post_mapper.md

@@ -1,44 +1,44 @@
-Add cloud resource and scan results in the assets module for a system
-
-Endpoint request parameters/fields
-
-Field                   Data Type  Details
--------------------------------------------------------------------------------------------------
-systemId                 Integer   [Required] Unique eMASS identifier. Will need to provide correct number.
-containerId              String    [Required] Unique identifier of the container.
-containerName            String    [Required] Friendly name of the container.
-time                     Date      [Required] Datetime of scan/result. Unix date format.
-
-podName                  String    [Optional] Name of pod (e.g. Kubernetes pod).
-podIp                    String    [Optional] IP address of pod.
-namespace                String    [Optional] Namespace of container in container orchestration (e.g. Kubernetes namespace).
-
-tags                     Object    [Optional] Informational tags associated to results for other metadata.
-  text                   String    [Optional] Tag metadata information.
-
-benchmarks               Object
-  benchmark              String    [Required] Identifier of the benchmark/grouping of compliance results. 
-                                   (e.g. for STIG results, provide the benchmark id for the STIG technology).
-  isBaseline             Boolean   [Optional] True/false flag for providing results as baseline. If true, all existing
-                                   compliance results for the provided benchmark within the container will be replaced
-                                   by results in the current call.
-  results                Object                                 
-    ruleId               String    [Required] Identifier for the compliance result, vulnerability, etc.
-    status               String    [Required] Benchmark result status
-    lastSeen             Date      [Required] Date last seen, Unix date format
-    message              String    [Optional] Comments for the result
-
-The following Container parameters/fields have the following character limitations:
-- Fields that can not exceed 100 characters:
-  - STIG Benchmark ID      (`benchmark`)
-  - Container Namespace    (`namespace`)
-  - Kubernetes assigned IP (`podIp`)
-  - Kubernetes Pod Name)   (`podName`)
-- Fields that can not exceed 500 characters:
-  - Container ID              (`containerId`)
-  - Friendly Container Name   (`containerName`)
-- Fields that can not exceed 1000 characters:
-  - Result Comments (`message`)
-
-Example:
-bundle exec ruby exe/emasser post container add --systemId [value] --containerId [value] --containerName [value] --time [value] --benchmark [value] --lastSeen [value] --ruleId [value] --status [value]
+Add cloud resource and scan results in the assets module for a system
+
+Endpoint request parameters/fields
+
+Field                   Data Type  Details
+-------------------------------------------------------------------------------------------------
+systemId                 Integer   [Required] Unique eMASS identifier. Will need to provide correct number.
+containerId              String    [Required] Unique identifier of the container.
+containerName            String    [Required] Friendly name of the container.
+time                     Date      [Required] Datetime of scan/result. Unix date format.
+
+podName                  String    [Optional] Name of pod (e.g. Kubernetes pod).
+podIp                    String    [Optional] IP address of pod.
+namespace                String    [Optional] Namespace of container in container orchestration (e.g. Kubernetes namespace).
+
+tags                     Object    [Optional] Informational tags associated to results for other metadata.
+  text                   String    [Optional] Tag metadata information.
+
+benchmarks               Object
+  benchmark              String    [Required] Identifier of the benchmark/grouping of compliance results. 
+                                   (e.g. for STIG results, provide the benchmark id for the STIG technology).
+  isBaseline             Boolean   [Optional] True/false flag for providing results as baseline. If true, all existing
+                                   compliance results for the provided benchmark within the container will be replaced
+                                   by results in the current call.
+  results                Object                                 
+    ruleId               String    [Required] Identifier for the compliance result, vulnerability, etc.
+    status               String    [Required] Benchmark result status
+    lastSeen             Date      [Required] Date last seen, Unix date format
+    message              String    [Optional] Comments for the result
+
+The following Container parameters/fields have the following character limitations:
+- Fields that can not exceed 100 characters:
+  - STIG Benchmark ID      (`benchmark`)
+  - Container Namespace    (`namespace`)
+  - Kubernetes assigned IP (`podIp`)
+  - Kubernetes Pod Name)   (`podName`)
+- Fields that can not exceed 500 characters:
+  - Container ID              (`containerId`)
+  - Friendly Container Name   (`containerName`)
+- Fields that can not exceed 1000 characters:
+  - Result Comments (`message`)
+
+Example:
+bundle exec ruby exe/emasser post container add --systemId [value] --containerId [value] --containerName [value] --time [value] --benchmark [value] --lastSeen [value] --ruleId [value] --status [value]