SLATE Change Management Policy

VersionCommentEffective Date
1.0Initial VersionSeptember 25, 2020

All physical and virtual machines making up the SLATE platform should be managed with appropriate infrastructure automation software1, with the corresponding configuration stored so that its history is available for review and changes can be reverted if necessary2.

Software packages critical to the function of those machines, or otherwise externally exposed must be promptly updated to patch known vulnerabilities. Otherwise, all such software should be periodically updated when new versions become available unless doing so interferes with the functionality of the platform, in which case the conflict should be corrected to allow updates to occur.

1 Currently Puppet
2 Configuration is currently stored in MWT2’s GitLab