CIS Control 16: Application Software Security
If you build or customize software, including HCL Domino applications, this control makes sure security is part of how it is designed, built, tested and updated.
What it means
Manage the security life cycle of software you develop, host or acquire, so you can prevent, detect and fix security weaknesses before they affect your organization.
Why it matters
Custom and in-house applications often hold your most important data and processes, but they rarely get the same security attention as off-the-shelf software.
Key safeguards (Control 16 begins in IG2)
Establish and maintain a secure application development process (IG2)
Establish a process to accept and address software vulnerabilities, and perform root cause analysis (IG2)
Maintain an inventory of third-party software components, and use up-to-date, trusted components (IG2)
Use a severity rating system and standard hardening templates (IG2)
Separate production and non-production systems, and train developers in secure coding (IG2)
Apply secure design principles, and use vetted modules and services (IG2)
Code-level security checks, application penetration testing and threat modeling (IG3)
How Prominic helps
Domino application reviews and testing during upgrades to Domino 2026
Separate test and production environments on our private cloud
Hosting applications on current, supported platforms
Secure development reviews for custom applications: details to confirm
Where it fits
Control 16 starts in IG2: it matters most for organizations that build or heavily customize software.
See also: Control 2: Inventory and Control of Software Assets, and Control 18: Penetration Testing.
