{"action":"closed","issue":{"url":"https://api.github.com/repos/GEOINT/gf-audit/issues/3","labels_url":"https://api.github.com/repos/GEOINT/gf-audit/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/GEOINT/gf-audit/issues/3/comments","events_url":"https://api.github.com/repos/GEOINT/gf-audit/issues/3/events","html_url":"https://github.com/GEOINT/gf-audit/issues/3","id":55937565,"number":3,"title":"Add confidentiality support to each data record (SRG-APP-000126-AS-000085)","user":{"login":"smsiebe","id":1139369,"avatar_url":"https://avatars.githubusercontent.com/u/1139369?v=3","gravatar_id":"","url":"https://api.github.com/users/smsiebe","html_url":"https://github.com/smsiebe","followers_url":"https://api.github.com/users/smsiebe/followers","following_url":"https://api.github.com/users/smsiebe/following{/other_user}","gists_url":"https://api.github.com/users/smsiebe/gists{/gist_id}","starred_url":"https://api.github.com/users/smsiebe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smsiebe/subscriptions","organizations_url":"https://api.github.com/users/smsiebe/orgs","repos_url":"https://api.github.com/users/smsiebe/repos","events_url":"https://api.github.com/users/smsiebe/events{/privacy}","received_events_url":"https://api.github.com/users/smsiebe/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-01-29T18:29:21Z","updated_at":"2015-05-08T17:21:06Z","closed_at":"2015-05-08T17:21:06Z","body":"This rule isn't really written well as it address confidentiality (encryption) and data integrity (hashing) as having a single-step solution.  This issue is specifically requesting that each log record can be encrypted to add confidentiality.\r\n\r\nRule Title:  The application server must use cryptographic mechanisms to protect the integrity of log information.\r\nSTIG ID: SRG-APP-000126-AS-000085 \r\n Rule ID: SV-46504r2_rule  \r\nVuln ID: V-35217\r\n\r\nDiscussion: \r\nProtection of log records is of critical importance. Encrypting log records provides a level of protection that does not rely on host-based protections that can be accidentally misconfigured, such as file system permissions. Cryptographic mechanisms are the industry-established standard used to protect the integrity of log data. An example of a cryptographic mechanism is the computation and application of a cryptographic-signed hash using asymmetric cryptography.\r\n\r\nDocumentable: No\r\n\r\nCheck Content: \r\nReview the application server documentation and configuration to determine if the application server can protect log data using cryptographic means.\r\n\r\nIf the application server is not configured to encrypt and sign logs, this is a finding.\r\n\r\nFix Text: \r\nConfigure the application server to encrypt and sign logs."}}