85 Deny use of source routing. Prevent denial-of-service attacks. 86 Use technologies like firewalls and virtual local area networks (VLANs) to properly segment your organization’s network in order to increase compartmentalization (e.g., machines with access to business services like e-mail should not be on the same network segment as your SCADA machines). Routinely review and test your firewall rules to confirm expected behavior. Achieve network segmentation to achieve compartmentalization. 87 Separate development, test, and production environments. Avoid production data leaks into test environments. Have controls in place around access to and changes in the production environment. 88 Ensure channel security of critical communication with technologies like Transport Layer Security (TLS). Where possible, implement Public Key Infrastructure (PKI) to support two-way mutual certificate-based authentication between nodes on your network. Secure data in transit. 89 Ensure availability of data traversing your networks. If a proper acknowledgement (ACK) is not received from the destination node, ensure that provisions are in place to resend the packet. If that still does not work, reroute the packet via a different network link. Implement proper physical security controls to make your network links harder to compromise. Detect failures and promote fault tolerance.
118 If possible, verify integrity of firmware running on field equipment via remote attestation techniques. Consult with the equipment vendor for assistance. If remote attestation fails, the affected field device should be considered compromised and should be isolated. Maintain confidence in data coming from field devices by ensuring that they have not been tampered with. The table below outlines the activities and controls that are currently missing from the platform security plan of the organization. Each activity row includes columns that describe the plan to implement the activity, the schedule for implementation, and the party responsible for its implementation and maintenance. Activity / Security Control Existing Guideline Deviation Accept or Mitigate Risk Responsible Party Estimated Completion Date Mitigation Strategy
130 Data arriving to be stored in the MDM system are syntactically and semantically valid. Prevent storing bad data in the MDM system and prevent potentially harmful / malicious data from compromising the system. 131 The system parsing the data arriving in the MDM system should make use of all appropriate data validation and exception-handling techniques. Prevent storing bad data in the MDM system and prevent potentially harmful / malicious data from compromising the system. 132 The MDM system has been designed and implemented using security-aware SDLC. Prevent storing bad data in the MDM system and prevent potentially harmful / malicious data from compromising the system. 133 Cleanse data stored in the MDM system of all private information. Promote user privacy. 134 Ensure that data arriving to be stored in the MDM system do not come from a compromised meter. Only data from uncompromised meters are stored in the MDM system. 135 The MDM system has passed a security penetration test conducted by a qualified third party. Prevent storing bad data in the MDM system and prevent potentially harmful / malicious data from compromising the system. 136 Gracefully handle denial-of-service attempts (from compromised meters). Protect the MDM system from attacks originating from smart meters. The table below outlines the activities and controls that are currently missing from the meter data management plan of the organization. Each activity row includes columns that describe the plan to implement the activity, the schedule for implementation, and the party responsible for its implementation and maintenance.
Activity / Security Control Existing Guideline Deviation Accept or Mitigate Risk Responsible Party Estimated Completion Date Mitigation Strategy (IHD) / The following checklist summarizes the various security best practices and controls that an organization should consider implementing. For more details on any of the activities / security controls, please refer to the descriptions in the Guide to Developing a Cyber Security and Risk Mitigation Plan. ID Activity / Security Control Rationale Associated Documentation 163 Ensure the integrity of data shown on users’ IHDs. Protect the integrity of data sent to the user. 164 Ensure the anonymity and privacy of data (where appropriate) pertaining to electricity usage patterns such that they cannot be tied back to the consumer. Protect the privacy of users’ electrical usage data. 165 Ensure that the software running on IHDs is free of weaknesses, especially if these weaknesses are remotely exploitable. Ensure that attackers cannot remotely control the IHDs of users. 166 If the IHD can send data upstream (an unusual configuration), ensure the integrity of such communication. Protect the integrity of data received from the user.