IdExchange 1.9.1

IDMS Security Vulnerability Identification and Resolution Process Overview

This document provides information on how every IDMS release is checked for known vulnerabilities, how the security process improves the ability to detect security risks and reduces the risk of releasing an unsafe build, and how fixes reach customer environments.

Summary

  • Every build is checked automatically against public vulnerability databases, covering the software IDMS uses directly and their dependencies.

  • High and critical vulnerabilities stop the build. The build is halted until the issue is remediated. This check is automated in the build system rather than relying on manual review alone.

  • Every image is built on a freshly downloaded, vendor-patched operating system base. Each build pulls the newest one; nothing is reused from an old copy.

  • A new build contains the security remediations with a standard update. The customer pulls the new IDMS container image and restarts, and the patched release is running.

Why this matters

Modern software is assembled from many components: Microsoft's .NET platform, cryptography libraries, communication libraries and the operating system inside the container. The process scans these components for newly disclosed vulnerabilities on every build, including components several layers removed from the code our engineers write.

The process is designed on the expectation that new vulnerabilities will continue to be disclosed. Each build is checked against current advisory data, builds containing serious known issues are halted, and the path from remediation to customer deployment is kept short.

The lifecycle at a glance

  1. New build

  2. Automatic vulnerability check

  3. Vulnerability found: build halted

  4. Component updated and verified

  5. Build passes: new image published

  6. Customer pulls update

1. Detection: every build is checked

Each time IDMS is built, the build system compares every software component against the public vulnerability advisory database that covers the .NET ecosystem. It checks the advisory data as it stands at that moment, so a vulnerability disclosed yesterday is caught by today's build, even if no IDMS code has changed.

The check covers two kinds of components:

  • Direct components: the libraries IDMS explicitly uses.

  • Indirect components: the libraries those libraries depend on.

2. Enforcement: halting builds with serious findings

Findings are handled according to the industry-standard severity rating attached to each advisory:

Severity

What happens

Critical

The build is halted until the finding is remediated.

High

The build is halted until the finding is remediated.

Moderate

Reported to the engineering team on every build and reviewed for remediation.

Low

Reported to the engineering team on every build and reviewed for remediation.

A halted build produces no container image, which reduces the risk of a build with a known serious vulnerability reaching customers. The expected path forward is to remediate the finding; engineering practice is to fix the component rather than weaken the check to get a build through.

Automated checks can only detect vulnerabilities that have been publicly disclosed and recorded in advisory databases. For that reason this process is one layer of a broader security approach, not a guarantee that every risk is eliminated.

3. Remediation: fixing the issue

  1. Identify. The failed build names the affected component, the advisory and the fixed version. Engineering assesses whether IDMS actually uses the vulnerable feature. We record that assessment, but the practice is to update the component either way rather than rely on "it isn't used" as the reason to leave a known vulnerability in place.

  2. Update. The component is moved to the vendor's patched version. All component versions are managed in a single central place, so one change applies consistently across the whole product. Where an indirect component is vulnerable, we explicitly require the patched version to help prevent the older one from being reintroduced.

  3. Verify. The product is rebuilt and the vulnerability check runs again to confirm the advisory is resolved and no new known advisories were introduced. Changes to security-sensitive areas such as cryptography, certificates and identity get additional review.

  4. Record. Each remediation is logged with the date, the component, the advisory, the old and new versions and the verification performed. This gives an auditable history of every security update.

4. Release: the build proceeds

Once the vulnerability check passes, the build continues normally. IDMS is packaged as a container image and published to CyberArmed's private image registry, where it is available only to authorized customers. Each release gets its own version label, so it is always clear exactly which build a deployment is running.

5. Protecting the container's operating system

IDMS runs inside a container built on Microsoft's official .NET base image. That base image includes a minimal operating system layer, which can have vulnerabilities of its own.

Always the latest base

Every IDMS build downloads the newest version of Microsoft's base image instead of reusing a stored copy. Microsoft's operating-system and runtime security patches are picked up automatically on the next build.

When an image issue is found

If a vulnerability is reported in the container image, we rebuild IDMS against the latest patched base image and publish a new release. The fix is delivered the same way as any other update.

Runtime advisories

When Microsoft patches the .NET runtime itself, a rebuild picks up the patched runtime. An updated image is published so customer deployments can move off the affected runtime.

6. Delivery: how the fix reaches customers

Updating IDMS is a short, standard procedure that doesn't require reinstalling:

  1. Notification. CyberArmed notifies customers that a new release is available and, for security releases, what it addresses.

  2. Pull the new image. The customer's administrator downloads the updated IDMS image from the CyberArmed registry with a standard Docker pull, using the updated configuration file CyberArmed provides for that release.

  3. Restart. IDMS is restarted on the new image. Existing configuration and data are kept, and the patched release is now running.

Summary of the process

  • The automated build process checks every build for known vulnerabilities in all components, including indirect ones.

  • Builds with known high or critical vulnerabilities are automatically halted, reducing the risk of releasing an unsafe build.

  • Builds and image packaging use the latest vendor-patched operating system and runtime base.

  • Fixes are delivered through a standard image update.