What approach best implements secure software development practices for utility control systems?

What approach best implements secure software development practices for utility control systems?

• A. Rely solely on perimeter firewalls and intrusion detection for security.
• B. Perform security only during final testing before release.
• C. Accept unverified third-party components to speed deployment.
• D. Use a secure SDLC with code reviews, vulnerability scanning, dependency management, signed builds, and restricted deployment with change controls.

Answer: (D)

Security must be built into the software development lifecycle of utility control systems. This means integrating security practices at every stage—design, code, build, and deployment—to prevent vulnerabilities, verify what is being used, and maintain integrity over time. The best approach combines multiple, ongoing controls: code reviews catch mistakes or insecure designs early; vulnerability scanning automatically identifies known weaknesses in code and components; dependency management tracks and verifies third-party libraries and their versions to avoid risky or outdated components; signed builds ensure the code’s origin and integrity; and change controls with restricted deployment enforce approvals and limit who can push changes, reducing the chance of unauthorized or disruptive updates. Together, these practices create a defensible, auditable process that matches the high-stakes nature of utility control systems. Relying solely on perimeter firewalls and IDS leaves gaps, since threats can originate inside the network or come from unpatched or insecure software. Doing security only at the end misses issues that were introduced earlier in the development cycle. Accepting unverified third-party components introduces unknown risks and supply-chain weaknesses. The comprehensive secure SDLC approach addresses these problems by embedding security throughout development and deployment.

Security must be built into the software development lifecycle of utility control systems. This means integrating security practices at every stage—design, code, build, and deployment—to prevent vulnerabilities, verify what is being used, and maintain integrity over time.

The best approach combines multiple, ongoing controls: code reviews catch mistakes or insecure designs early; vulnerability scanning automatically identifies known weaknesses in code and components; dependency management tracks and verifies third-party libraries and their versions to avoid risky or outdated components; signed builds ensure the code’s origin and integrity; and change controls with restricted deployment enforce approvals and limit who can push changes, reducing the chance of unauthorized or disruptive updates. Together, these practices create a defensible, auditable process that matches the high-stakes nature of utility control systems.

Relying solely on perimeter firewalls and IDS leaves gaps, since threats can originate inside the network or come from unpatched or insecure software. Doing security only at the end misses issues that were introduced earlier in the development cycle. Accepting unverified third-party components introduces unknown risks and supply-chain weaknesses. The comprehensive secure SDLC approach addresses these problems by embedding security throughout development and deployment.