ID.AM-08.142

Does your organization have a formal pre-deployment security hardening process for all systems, hardware, software, and services before they enter production?

Explanation

Hardening before go-live is the point of this item, namely whether you run a formal pre-deployment security hardening process for systems, hardware, software, and services entering production.

Proper pre-deployment hardening includes activities such as removing unnecessary services, applying security patches, configuring secure authentication, implementing least privilege access controls, and ensuring secure network configurations.As evidence, you could provide documentation of your pre-deployment security checklist, hardening standards for different system types, screenshots of configuration management tools, or sample security validation reports that must be completed before production deployment approval.

Implementation Example

Properly configure and secure systems, hardware, software, and services prior to their deployment in production

ID: ID.AM-08.142

Context

Function
ID: IDENTIFY
Category
ID.AM: Asset Management
Sub-Category
Systems, hardware, software, services, and data are managed throughout their life cycles

Related questions

ResponseHub is the product I wish I had when I was a CTO

Previously I was co-founder and CTO of Progression, a VC backed HR-tech startup used by some of the biggest names in tech.

As our sales grew, security questionnaires quickly became one of my biggest pain-points. They were confusing, hard to delegate and arrived like London busses - 3 at a time!

I'm building ResponseHub so that other teams don't have to go through this. Leave the security questionnaires to us so you can get back to closing deals, shipping product and building your team.

Signature
Neil Cameron
Founder, ResponseHub
Neil Cameron