Skip to main content

Lack of Automation Undermines Network Configuration Compliance

Rich Martin
Itential

Most enterprise IT organizations struggle with network and cloud infrastructure configuration management and worry that their networks will fail configuration compliance audits. This issue is amplified as enterprise network engineers continue to take the "if it's not broke, don't fix it" approach to network infrastructure management. With that said, companies are beginning to demand more from their networks. Enterprise IT organizations are seeking out solutions that will enable them to be more agile and secure. As a result, infrastructure and operations teams are turning to network automation solutions.

Key findings from an Itential State of Network Automation survey demonstrate that any network automation initiative should include automated configuration compliance enforcement as a foundational building block. Moreover, configuration compliance should be applied to automation initiatives across any part of the network, from the data center to the cloud and out to the edge. By further analyzing the results of this report, organizations gain a better understanding on why such capabilities are necessary and how to make strides towards such solutions.

Outlining Current Setbacks

Selecting the right tools to utilize as part of the network automation management process is not always a straightforward task. Network engineers need to consider the complexity of the environment, those who will be managing it, operational processes, etc. In fact, only 34% of network management professionals are completely satisfied with the tools and processes they use for network configuration management. Network complexity also impacts the effectiveness of network configuration management, and as such, satisfaction is lowest in the largest networks. With more devices under management, changes can take longer and are more prone to error and this dissatisfaction leads to high anxiety. Three out of four IT organizations are at least somewhat concerned that their configuration management process could cause errors that lead to security issues or performance problems.

Of course, most IT organizations know their network configuration management processes need improvement. The report found that more than 60% of respondents are not confident that major parts of their networks could pass compliance audits, particularly in the data center and public cloud domains. This proves that organizations know they are at risk of fatal errors when it comes to operating their network successfully. The question remains, how can this be fixed?

Considering Next Steps

Configuration compliance is an essential starting point. Network engineers and architects generally know the intent of their network. They know how they want the network to behave and what network and security policies they want to enforce, but they aren't confident in their network's ability to comply with their intent. Reducing or eliminating manual configuration management processes can improve audit compliance and set up a technology organization for a successful network automation initiative. By enabling end-to-end automation across hybrid infrastructure, teams can ensure the consistency of network configuration compliance and accelerate processes like self-service networking.

Operational efficiency and reduced security risk must be top priorities. Automation can streamline operations by reducing time spent on repetitive tasks, allowing engineers to focus on strategic work. It can also reduce security risks by ensuring network device and service configurations adhere to strict security standards. Knowing that another 75% of organizations believe that self-service networking enabled by northbound APIs on network automation solutions will be at least somewhat helpful to IT operations, organizations can move forward knowing they will ultimately have the support they need to make such advancements.

Network automation can drive operational efficiency, reduce security risk, and improve compliance. It is crucial for IT organizations to identify their priorities for using network automation to transform operations. Then, they can let those priorities guide their network automation initiatives.

Rich Martin is Director of Technical Marketing at Itential

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Lack of Automation Undermines Network Configuration Compliance

Rich Martin
Itential

Most enterprise IT organizations struggle with network and cloud infrastructure configuration management and worry that their networks will fail configuration compliance audits. This issue is amplified as enterprise network engineers continue to take the "if it's not broke, don't fix it" approach to network infrastructure management. With that said, companies are beginning to demand more from their networks. Enterprise IT organizations are seeking out solutions that will enable them to be more agile and secure. As a result, infrastructure and operations teams are turning to network automation solutions.

Key findings from an Itential State of Network Automation survey demonstrate that any network automation initiative should include automated configuration compliance enforcement as a foundational building block. Moreover, configuration compliance should be applied to automation initiatives across any part of the network, from the data center to the cloud and out to the edge. By further analyzing the results of this report, organizations gain a better understanding on why such capabilities are necessary and how to make strides towards such solutions.

Outlining Current Setbacks

Selecting the right tools to utilize as part of the network automation management process is not always a straightforward task. Network engineers need to consider the complexity of the environment, those who will be managing it, operational processes, etc. In fact, only 34% of network management professionals are completely satisfied with the tools and processes they use for network configuration management. Network complexity also impacts the effectiveness of network configuration management, and as such, satisfaction is lowest in the largest networks. With more devices under management, changes can take longer and are more prone to error and this dissatisfaction leads to high anxiety. Three out of four IT organizations are at least somewhat concerned that their configuration management process could cause errors that lead to security issues or performance problems.

Of course, most IT organizations know their network configuration management processes need improvement. The report found that more than 60% of respondents are not confident that major parts of their networks could pass compliance audits, particularly in the data center and public cloud domains. This proves that organizations know they are at risk of fatal errors when it comes to operating their network successfully. The question remains, how can this be fixed?

Considering Next Steps

Configuration compliance is an essential starting point. Network engineers and architects generally know the intent of their network. They know how they want the network to behave and what network and security policies they want to enforce, but they aren't confident in their network's ability to comply with their intent. Reducing or eliminating manual configuration management processes can improve audit compliance and set up a technology organization for a successful network automation initiative. By enabling end-to-end automation across hybrid infrastructure, teams can ensure the consistency of network configuration compliance and accelerate processes like self-service networking.

Operational efficiency and reduced security risk must be top priorities. Automation can streamline operations by reducing time spent on repetitive tasks, allowing engineers to focus on strategic work. It can also reduce security risks by ensuring network device and service configurations adhere to strict security standards. Knowing that another 75% of organizations believe that self-service networking enabled by northbound APIs on network automation solutions will be at least somewhat helpful to IT operations, organizations can move forward knowing they will ultimately have the support they need to make such advancements.

Network automation can drive operational efficiency, reduce security risk, and improve compliance. It is crucial for IT organizations to identify their priorities for using network automation to transform operations. Then, they can let those priorities guide their network automation initiatives.

Rich Martin is Director of Technical Marketing at Itential

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...