Management · Management Operations
Configuration and baseline records
Owned configuration records and approved baselines used to compare intended settings with the operating environment.
Features and benefits
| Feature | Practical benefit |
|---|---|
| Baseline definitions | Records the settings and dependencies a service is expected to use. |
| Version and relationship records | Connects configuration changes to assets, owners and dependent services. |
| Drift review | Helps identify unauthorized changes and track approved exceptions. |
Configuration and baseline records
Connect the service function to its practical benefit and a checked operating result.
Requirements → deployment → operation → validation
Document library
Requirements and security baseline
Configuration and baseline records Requirements and security baseline
Baseline alignment. Approved baseline revisions, validation evidence and documented exceptions. CIS IGs · DISA STIGs · DISA SRGs
- Baseline definitions: scope, supported systems and accountable owners
- Version and relationship records: approved settings, access and dependencies
- Drift review: acceptance criteria, retention and exceptions
Deployment and control mapping
Configuration and baseline records Deployment and control mapping
- Scope and ownership: Owned configuration records and approved baselines used to compare intended settings with the operating environment.
- Approved rollout and acceptance: Controlled pilot covering baseline definitions and version and relationship records; acceptance test: compare a sampled live configuration with its approved baseline and resolve or approve each material difference.
- Applicable requirements mapped to configuration, validation evidence and approved exceptions
Client and user guide
Configuration and baseline records Client and user guide
- Using baseline definitions within the approved service scope
- Recognizing failures and reporting a support request
- User responsibilities, access limits and service acceptance
Technician training outline
Configuration and baseline records Technician training outline
- Baseline definitions: records, configuration and diagnostic checks
- Version and relationship records: authorized administration and exception handling
- Drift review: validation, evidence and service handoff
RDA technician workflow
Configuration and baseline records RDA technician workflow
- Identify and assess the requirement; plan the scope, accountable owner and required approvals
- Implement and verify: Compare a sampled live configuration with its approved baseline and resolve or approve each material difference.
- Document the configuration and result; hand off operation, review exceptions and plan lifecycle changes
Portal and access training
Configuration and baseline records Portal and access training
- Named operators, role boundaries and multifactor access where supported
- Service identities, protected credentials and emergency access
- Access approval, periodic review and removal
Training module template
Configuration and baseline records Training module template
- Learning objectives and prerequisites: baseline definitions: records, configuration and diagnostic checks
- Authorized practical exercise: Compare a sampled live configuration with its approved baseline and resolve or approve each material difference.
- Knowledge check, observed result and instructor or responsible-owner sign-off
Basic installation and acceptance
Configuration and baseline records Basic installation and acceptance
- Approved platform, owner, permissions and prerequisite checks
- Controlled pilot covering baseline definitions and version and relationship records
- Acceptance test: Compare a sampled live configuration with its approved baseline and resolve or approve each material difference.
Advanced deployment and changes
Configuration and baseline records Advanced deployment and changes
- Extend baseline definitions to additional approved scope
- Change version and relationship records with impact review and rollback
- Validate drift review after an approved change
Technical configuration and integrations
Configuration and baseline records Technical configuration and integrations
- Baseline definitions: configuration and dependency records
- Version and relationship records: supported interfaces and permission boundaries
- Drift review: diagnostic collection, retention and evidence export
Operational audit and checklist
Configuration and baseline records Operational audit and checklist
- Coverage and operating checks: baseline definitions: coverage, health and unresolved exceptions
- Evidence sample: approved baseline and current configuration export; drift findings, change authorization and corrective retest
- Review date and owner; pass or fail, exceptions, corrective action and retest evidence
Tabletop exercises
Configuration and baseline records Tabletop exercises
- A required dependency or responsible provider becomes unavailable
- An access or configuration change interrupts the service
- Reported success conflicts with the observed business result
Response playbook
Configuration and baseline records Response playbook
- Assess the affected scope, evidence and business impact
- Authorize corrective action, escalation or rollback
- Verify service recovery, retain evidence and update the baseline
Operational runbooks
Configuration and baseline records Operational runbooks
- Validate baseline definitions against the approved design
- Investigate a failure affecting version and relationship records
- Collect drift review evidence and confirm service acceptance
Evaluation and lifecycle review
Configuration and baseline records Evaluation and lifecycle review
Selection and fit. Compare viable options against the business need, security requirements, existing systems and full operating cost. Record the reasons for the selection, the tradeoffs accepted and the conditions that would prompt a different choice.
Keeping the choice current. Follow supplier notices between scheduled reviews and reassess before renewal or a material change. Check ownership changes, renamed or retired products, subscription and licensing terms, pricing, capabilities and support commitments. Record the effect on security, data handling, integrations and service continuity. Assign an owner to approve adjustments or plan a transition, including data export and removal of access.
- Measured service outcome and practical acceptance results
- Supported scope, access, evidence availability and dependencies
- Licensing or provider terms, maintenance effort and lifecycle cost