SDN Controller Trusted Credential Issuance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern electric power transmission and distribution systems face security concerns due to the potential for cyberattacks, as they rely on software-defined networks (SDNs) that require secure communication between controllers and devices to prevent unauthorized data flow changes and ensure network integrity.
Innovation Solution
Establishing and maintaining trusted relationships within SDNs by using a controller as a trusted authority, issuing trusted credentials, and implementing public key infrastructure (PKI) to encrypt communications and verify device identities, with mechanisms for revoking credentials and reestablishing trust in case of compromised certificates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual configuration of trusted relationships is implemented in SDN, then security is improved, but device complexity and configuration burden increase
Solution Approach 1:
The SDN controller automatically performs certificate issuance, credential distribution, and trust relationship establishment without requiring manual configuration. The controller self-services the security setup by programmatically provisioning cryptographic materials to network devices, eliminating the need for operators to manually configure trusted relationships while maintaining strong security credentials
Solution Approach 2:
The system pre-establishes trust anchors and root certificates in the SDN controller before network devices join. When a new device connects, the trust relationship is automatically instantiated based on pre-configured security policies and cryptographic infrastructure, eliminating the need for real-time manual security configuration
2Reliability
If cryptographic credentials are distributed to all devices, then trust verification is improved, but loss of time for credential management increases
Solution Approach 1:
Network devices automatically receive and install cryptographic credentials through automated provisioning processes. The SDN controller pushes certificates and cryptographic materials to devices as needed, and devices automatically integrate these credentials into their security stacks without requiring manual installation or configuration time
Solution Approach 2:
The SDN controller maintains a centralized repository of cryptographic credentials and pre-prepares signing certificates before they are needed. When a device requires verification, the controller instantly provides pre-computed cryptographic materials, eliminating the time required for on-demand certificate generation and distribution
3Reliability
If primary signing certificate is compromised, then security is weakened, but system downtime increases without hot-warm standby
Solution Approach 1:
The SDN controller maintains hot-warm standby signing certificates that are pre-configured and ready for immediate activation. If the primary signing certificate is compromised, the controller can instantly switch to a standby certificate without system downtime, as the failover mechanism is pre-established and tested
Solution Approach 2:
The standby signing certificates act as intermediaries that can temporarily assume the role of the compromised primary certificate. These intermediary credentials allow the system to maintain operational security functions while the primary certificate is being revoked and replaced, preventing service interruption
Data Source
AI summary
The present disclosure pertains to systems and methods for establishing trust relationships between a software defined network (SDN) controller and a SDN communication device. In one embodiment, a SDN controller may comprise a communications interface configured to communicate with a plurality of SDN network devices. A commissioning subsystem configured to detect a new device associated with the SDN. In response to a new device, a user interface subsystem may be configured to receive a user approval to commission the new device. A trust subsystem configured to establish a first SDN controller trusted credential and to transmit a first device trusted credential based on the first SDN controller credential to the new device. Programming instructions to the new device authenticated using the first SDN controller trusted credential by a SDN programming subsystem.