SolarWinds announced multiple products are now certified under the Common Criteria for Information Technology Security Evaluation (ISO/IEC 15408), an internationally recognized standard for computer security achieved through independent laboratory testing and evaluation.
“At SolarWinds, we make every effort to ensure our software is powerful, effective and safe,” said Chris LaPoint, VP Product Management, SolarWinds. “This Common Criteria certification attests that SolarWinds solutions adhere to the necessarily high performance standards for government deployment and are validated to help IT Pros accomplish their missions.”
Common Criteria provides a broad range of evaluation criteria for commercial and nationally sensitive government-use IT security products. Federal IT users needing to run applications in National Security Systems (NSS) environments can look to Common Criteria-certified software for numerous compliant software solutions.
The SolarWinds Orion Suite, comprising the below solutions, is now certified under Common Criteria lab EAL 2 evaluation, empowering government IT pros to implement and use the software safely on Federal networks:
- Network Performance Monitor 10.6 – Management and monitoring of dynamic network performance
- Server & Application Monitor 6.0 – Server, application and OS monitoring
- Network Configuration Manager 7.2 – Network configuration and compliance management
- Network Traffic Analyzer 3.11 – Flow-based network traffic analysis
- IP Address Manager 4.0 – IP address and DHCP/DNS management and monitoring
- User Device Tracker 3.0.1 – Device and switch port monitoring and mapping
- VoIP & Network Quality Manager 4.1 – VoIP and WAN performance monitoring
- Web Performance Monitor 2.0.1 – Website and web application monitoring
- Enterprise Operations Console 1.4.1 – Unified management for distributed enterprise networks
- Failover Engine 6.7.0 – SolarWinds platform server monitoring
SolarWinds Log & Event Manager 5.7, which provides log collection, analysis and real-time correlation, is also Common Criteria certified under EAL 2+ lab testing.
Electronic Warfare Associates (EWA)-Canada, a Common Criteria Testing Laboratory (CCTL) accredited by the Standards Council of Canada and approved by Canada’s Communications Security Establishment (CSE), has evaluated the SolarWinds software to determine it meets all of the requirements of this security certification. EWA-Canada is recognized for its extensive experience with Common Criteria evaluations, enabling companies to manage the process and ensure their products meet important certification requirements.
“EWA-Canada is pleased to verify SolarWinds’ solutions as Common Criteria-certified,” stated Erin Connor, Director of the EWA-Canada CCTL. “During the rigorous evaluation process, SolarWinds solutions demonstrated their sophistication and high standards of quality and security. This independent certification reflects SolarWinds' commitment to providing high-quality solutions to support the mission-critical demands of IT professionals in the Federal Government and elsewhere and proves that the products meet global security standards for deployment in government.”
SolarWinds software is available on the U.S. General Services Administration (GSA) Schedule, Department of Defense ESI, and other contract vehicles.
U.S. Government certifications and approvals include Army CoN, Air Force APL, Navy DADMS; and Technical Requirements include FIPS compatibility, DISA STIGs, and National Institute of Standards and Technology (NIST) compliance.
SolarWinds also has hundreds of built-in automated compliance reports, which meet requirements of all major auditing authorities, including DISA STIG, FISMA, NIST, and more. SolarWinds’ thwack online user community provides a number of out-of-the-box compliance report templates available to download for free that are designed to help users prepare for an inspection. thwack also provides information on Smart Card and Common Access Card (CAC) product support.
The Latest
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.
The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...