| [MON-0] | The system design preventing data modification is documented in the technical documentation. |
| [MON-1] | Historical data import leaves a trace in the logs, if existing metric value was altered. |
| [MON-1] | National MSAs are able to validate the system design comformity without a deployment. |
Assessment:
**[MON-0]** Collected and stored metrics data can not be altered from the target.
Test: Review the documentation of all of the interfaces between the target and the collected and stored metrics data looking for any interface that may allow alteration of the metrics data after it has left the target.
Result: No interface allows the alteration of collected metrics data after it has left the target.
**[MON-1]** Historical metrics data imports are handled outside of the normal flow.
Test: Set up the product to provide output that distinguishes the method of handling both normal metrics data collection and historical data imports. Set up the product to collect metrics data in the normal manner from a client and begin collection. Collect output showing the whether the current metrics data is being handled by the normal flow. Now begin a historical data metrics import. Collect output showing the whether the current metrics data is being handled by the normal flow.
Result: Output shows that the historical data metrics import is being handled by a different flow from the current metrics data collection.
Output: Output showing which flow is being used to handle each of current metrics collection and historical metrics data import.
TBD:
| [MON-2] | National MSAs are able to validate the system design comformity without a deployment. |
| [MON-3] | National MSAs are able to validate the system design comformity without a deployment. |
| [MON-4] | <mark>How to define business continuity metrics? A new chapter?</mark> |
