Downloaded from https://www.everyspec.com ADS-79D-HDBK L.5.6 Security. In addition to accidental data corruption and loss during storage, data integrity may be compromised as a result of malicious attacks on the CBM system. Therefore, the proper design should ensure that security measures and procedures are implemented to prevent the willful, malicious destruction of maintenance data. These measures should include the implementation of either or both physical security and logical security. Physical security refers to the physical placement of the data storage system in a secure area where only authorized administrators have access.
Logical security refers to the implementation of user passwords or other authentication for data access. User passwords offer the ability of implementing a layered security by allowing different levels of access, including the ability to change or delete data, to different users. L.5.7 Data Retrieval. Data corruption and loss may occur during data retrieval; therefore, the design should incorporate the necessary precautions to ensure data integrity during data recall from storage and use. For example, modifications to the originally acquired data on retrieval and use should be documented with a date stamp before being returned to storage. L.5.8 Data Mining.
Stored data may be called upon at any time in its lifecycle for processing to obtain information about the observed event. Depending on the nature of the stored data, this could involve filtering of sampled measurements or queries of records in a database of processed measurements. The data should be oriented and formatted in a manner that allows access to the variety of authorized Army maintenance and analysis systems . However, as discussed as part of Data Retrieval (L.5.7), measures should be taken to ensure that data is not lost or corrupted as a product of data analysis.
For example, the data storage system may limit data mining to being performed on a copy of the archived data while retaining the original in order to guarantee integrity. L5.9 Data traceability Each critical parameter must be traceable from its source to the final usage destination (See Figure L-1). All data events to include translation transformation, or user manipulation should be traceable. A record that includes the description of the data, the date of the activity, and the identification of the person executing the activity should be logged. This will coincide with the end-to-end process. Data traceability can provide details or a tracking mechanism from the originator to the end-user.
Traceability is critical in identifying whether a component meets a required standard. Being able to trace information on a particular component can be very useful in determining if the data is consistent and accurate. 231