Summary
This page discusses risk and mitigation with changing discovery commands and ensuring that the right data is collected and processed by Tideway Foundation.
| | |
|---|
Availability of New Commands | - Attributes collected need new or amended discovery command
* New command has adverse affect on the OSI
| * Workshop and review purpose of command and lost value in not having it versus gain in having it
* Review customer security policies to ensure new/changed command is acceptable and doesn't cause security concern/breech
* Review with Tideway Product Management to confirm there are no plans to capture the same attributes via an alternative command in the future |
| - New command is used to collect untested attributes
* Change is deployed to inappropriate technology types
| * Confirm and agree with Sponsors on what attributes will be collected using new/changed command
* Confirm and document the technology types to be affected by the new/changed command
* Review impact on Foundation reasoning of new attributes |
| - New/changed command is not tested
* New/changed command causes impact after testing
| * Test all commands on the Tideway Dev/UAT environment against Lab technology
* Formally sign-off Dev/Lab testing with Sponsors before raising Production change request
* Deploy new/changed command to subsets of Production during out of hours scanning window
|
| - Inadequate skill and availability
* Ownership of technical issues
| * For new commands, complete planning to distribute into the environment
* Raise all necessary change requests prior to rolling out
* Update all Tideway project documentation to reflect details on the new/changed command
* Promote value of attributes being collected by the new/changed command through use of new reports, etc |
