Assessment preparation starts with the questions you need to answer. An enhanced requirement may involve several activities and evidence sources, so connect each part of the implementation with the objectives the assessor will examine. By leveraging SecureX7 Work Plans, tasks can be tracked and kept on track, with as much evidence being automatically gathered and applied from the knowledge built-up in your system.
SecureX7 contributes asset information, supported configuration checks and remediation guidance. Its System Integrity Monitoring function will also record hashes and metadata for all system files, alongside registry keys and values, installed software and local user accounts. These baseline records provide a forensic starting point for investigating changes, including changes that may be associated with stealthy APT activity.
Use the applicable assessment procedures
Confirm the required publication revisions and selected enhancements. Agree the agency-defined depth and coverage with the relevant parties, including any assessor independence requirements. The procedures applicable to your programme determine how evidence must be examined.
Build an evidence plan around assessment objectives
Your responsibilities for NIST 800-172 are to work from the determination statements for each selected requirement. Establish the relevant parameter values, then identify the records, mechanisms, activities and people that can provide evidence.
Examination, interview and testing all provide answers to different parts of the assessment question. One technical result may leave process or operational questions open. Record who owns each evidence item, how it will be collected, the systems it covers and its date.
Using a SecureX7 Work Plan will guide this entire process, with actionable guidance provided by the AI Assistant to make the journey as expert and easy as possible.
Connect integrity records with assessment questions
For selected integrity enhancements such as 03.14.01E, 03.14.08E and 03.14.09E, evidence may include baseline records, comparison results, integrity mechanism configuration and tests, check timing and records of action taken. Use the applicable 800-172A procedures to establish the complete evidence needed for each objective.
SX7 baselines all system files with a cryptographic hash for each file and all file metadata, together with registry keys and values, installed software and local user accounts. A changed file hash supports an investigation into content integrity, and you would naturally introduce IAM knowledge to provide a full Who/When/What/Where/Why for any changes that appear potentially unwanted.
Demonstrate how differences are investigated
Suppose the software inventory changes and a new local account appears. The owner checks deployment and access approval records, confirms the purpose and investigates anything unexplained. Keep the observations together with the review decision and action taken.
Where the assessment plan requires it, test the integrity mechanism using an authorised, controlled change and verify the observed result and response. Confirm checking frequency and relevant event coverage separately. A single comparison does not demonstrate continuous operation or every required response activity.
Make limitations clear to the assessor
Technical records contribute to the assessment; authorised parties determine their sufficiency and the assessment conclusion. Provide separate evidence for baseline validation, access to monitoring records, review responsibilities and response procedures. Confirm any firmware and wider information integrity coverage through the appropriate capabilities.
Explore the evidence behind system integrity monitoring
Ask us for a live work-through of an integrity-change assessment workflow. You will see how baseline and comparison records contribute to the evidence plan, and how the AI Assistant is on hand to short-cut incident investigation work.
