Baseline Reuse

Go to Terms and Definitions

Baseline Reuse applies the same identified Baseline Revision to two or more subjects, activities, or contexts without modifying the Baseline content.

Baseline Reuse may apply the same Baseline Revision to:

• Multiple Infrastructure Environments
• Multiple Machine Images
• Multiple deployments
• Multiple provider implementations
• Multiple organizational domains
• Repeated lifecycle activities
• Repeated compliance assessments

The subject-specific result may differ because of:

• Platform Specific Parameters
• Environment-specific values
• Permitted overrides
• Selected optional controls
• Context-specific constraints

Those differences remain separate from the reused Baseline content.

Baseline Reuse differs from copying and modifying a Baseline:

• Baseline Reuse applies the same Baseline Revision without changing its content
• Copying and modifying Baseline content creates a different candidate Baseline or Revision

Baseline Reuse also differs from Baseline Composition:

• Baseline Reuse applies the same Baseline Revision more than once
• Baseline Composition combines content from multiple Baselines

application of the same identified baseline revision to two or more subjects, activities, or contexts without modification of the baseline content

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

Baseline Reuse does not require identical resulting subjects.

The applicable requirements determine which subject-specific values may vary without changing the reused Baseline.

A revised Baseline is a different Revision and should remain distinguishable from the Baseline Revision previously reused.

A build workflow applies the same Security Baseline Revision to development, test, and production Machine Images while keeping environment-specific network and monitoring values separate from the Baseline content.