Merge pull request #114 from IanDavila/main

Fixing data components structure for ICS

contribution-ics/assets.yml

@@ -9,11 +9,9 @@ data_components:
   - name: Asset Inventory
     type: information
     description: "This includes sources of current and expected devices on the network, including the manufacturer, model, and necessary identifiers (e.g. IP, HW addresses)"
-data_components:
   - name: Software/Firmware
     type: information
     description: This includes sources of current and expected software, firmware, or application programs deployed to a device, along with information on the version and patch level for vendor products, full source code for any application programs, and unique identifiers (e.g., hashes, signatures)
-data_components:
   - name: Device Configurations/Parameters
     type: information
     description: This includes sources of both current and expected device configurations, parameters, or settings, including PLC tags

contribution-ics/operational_databases.yml

@@ -9,11 +9,9 @@ data_components:
   - name: Process History/Live Data
     type: information
     description: This includes any data stores that maintain historical or real-time events and telemetry recorded from various sensors or devices
-data_components:
   - name: Process/Event Alarm
     type: information
     description: "This includes a list of any process alarms or alerts produced to indicate unusual or concerning activity within the operational process (e.g., increased temperature/pressure)"
-data_components:
   - name: Device Alarm
     type: information
     description: This includes alarms associated with unexpected device functions, such as shutdowns, restarts, failures, or configuration changes