{
  "id": 15600674,
  "title": "Change is constant across your IT estate. But is it under control?",
  "url": "https://urgent.news/2026/10/19/change-is-constant-across-your-it-estate-but-is-it-under-control",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-19T11:04:12.000Z",
  "source": {
    "name": "TechRadar",
    "slug": "techradar",
    "url": "https://www.techradar.com/pro/change-is-constant-across-your-it-estate-but-is-it-under-control"
  },
  "original_language": "en",
  "account": "Change is a constant factor in any IT environment. It occurs constantly, from routine user permission adjustments to the integration of third-party software. External providers, outsourced teams, and employees also contribute to this change. While change is necessary for security, resilience, and modernization, unmanaged change can pose significant risks. It may go unnoticed, such as an automatic external patch, or be forced, like a rushed OS upgrade to meet an end-of-life deadline. Many organizations must monitor vast and intricate IT estates, which could include hundreds or thousands of critical business endpoints. The sheer volume of automated changes and those executed by external parties often leaves IT teams with limited visibility into many ongoing changes. These seemingly minor changes can accumulate over time, causing systems to deviate from their intended baseline. This drift increases system vulnerability, leading to potential failures and damaging outages. Moreover, non-managed changes also make systems more susceptible to cyber attacks. Misconfigurations or gaps in security coverage enable more than 90% of cyber incidents investigated in recent research, demonstrating how minor changes or oversight lapses can create vulnerabilities for attackers. To effectively control IT change, three crucial steps must be taken. First, IT teams must gain better visibility into change across the estate. This can be achieved through the use of automation tools that enable continuous drift detection. The technology must scan every layer of the infrastructure to establish a baseline configuration, allowing teams to monitor for configuration changes in real-time. Any drift from this baseline, along with the discrepancy between expected and actual changes, is flagged. This proactive approach ensures that manual fixes or external patches are not overlooked until they cause an outage or failure. Second, IT teams must respond swiftly to changes by automating the approval process. Manually reconciling and approving change can be error-prone and time-consuming, potentially delaying approvals. Automating change approval processes helps reduce manual effort by comparing every detected change to approved baselines and validating the steps taken against those planned in the change request. This accelerates the delivery of new upgrades or projects, enabling IT teams to innovate safely. Lastly, IT teams must protect their systems from potential cyber incidents. By understanding what's happening in the estate and streamlining approval processes, teams can detect and remediate issues faster, reducing mean time to resolution. This mitigates the risk of failure escalating into an outage or minimizing the cost of an incident, ultimately enhancing overall resilience. Ensuring compliance and maintaining a real-time audit trail is also crucial, as it provides defensible evidence for regulators and highlights the importance of continuous compliance. In conclusion, while change is inevitable and will only increase with the rapid development of AI and cloud tools, effectively managing change provides the foundation for safe and successful innovation.",
  "summary": "Change itself isn't a problem. Change that isn't actively managed, however, is a different story.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}