The primary consideration in determining whether a solution can be classified as static or dynamic is “flexibility.” In other words, can the solution be reconfigured or modified to respond to a dynamic environment without undergoing significant redevelopment (either at the logic level, data level or both). As we know from decades of IT experience, extending a static system through integration is very time consuming and costly. Yet Cyber threats change every day.
The problem encompasses both data and logic and each effect the other – usually requiring complex modifications every time in both directions to achieve updated capability. Most enterprises possess or utilize many individual static systems, thus the complexity associated with static design can extend to n levels or directions. In most cases, none of the static systems were specifically designed to operate in a larger environment (outside of dependence on several key data imports or exports).
Another way to look at Static versus Dynamic solutions is to examine how various systems and data support static versus dynamic processes or views of what’s occurring. The figure below illustrates that different systems can support or contribute to static or dynamic views and they can be directed at different functional domains.
Static solutions can provide important data, however they cannot adjust well to changing situations.
