# Continuous Integration and Continuous Deployment **Acronym:** CI/CD **Entity class:** Software delivery practice ## Definition **Continuous integration and continuous deployment (CI/CD)** automate the integration, testing, delivery, and deployment of software changes. The relevance to vulnerability management is architectural: new code, dependency intelligence, test results, patches, and verification evidence can continuously update the trusted state of a deployed system. ## Neurosecurity bridge [[wiki/Continuous Vulnerability Intelligence|Continuous vulnerability intelligence]] applies a similar cadence to security state. Each new observation can alter an exposure model; each vulnerability can trigger dependency analysis; each exploit can change priority; each patch can trigger verification; and each anomalous neural-interface state can initiate [[wiki/Neural Incident Response|incident response]]. ## Relationships - **security lifecycle:** [[wiki/Continuous Vulnerability Intelligence|Continuous Vulnerability Intelligence]]. - **component inventory:** [[wiki/Software Bill of Materials|Software Bill of Materials]]. - **medical-device context:** [[wiki/Medical Device Vulnerability Management|Medical Device Vulnerability Management]]. - **restoration:** [[wiki/Verified Neural Restoration|Verified Neural Restoration]]. ## Sources / Provenance - National Institute of Standards and Technology, [Secure Software Development Framework, SP 800-218](https://csrc.nist.gov/pubs/sp/800/218/final), 2022. - U.S. Food and Drug Administration, [Cybersecurity in Medical Devices FAQ](https://www.fda.gov/medical-devices/digital-health-center-excellence/cybersecurity-medical-devices-frequently-asked-questions-faqs), accessed 2026-09-23. **As of:** 2026-09-23