BeyondTrust

Security in Context: The BeyondTrust Blog

Welcome to Security in Context

Bringing you news and commentary on solutions and strategies for protecting critical IT infrastructure in the context of your business.

Multiple Platform Configuration Compliance

Posted April 27, 2011    Morey Haber

Here is the problem. Most small businesses benefit from picking a standard platform like Microsoft Windows and exclusively using it from laptops to servers. There has always been, even in the smallest companies, some resistance to Windows including the  rogue Mac users. Enterprises tend to pick the platform they need based on business requirements and standardization, and using the same platform becomes a secondary or even tertiary consideration. I am sure many of you have seen companies with “one of everything” and we use “these” platforms and if your application does not support it, we will not license “your” technology. It is similar to the infamous “religious” battle you hear between Windows and Unix staff. So with such a diverse requirement for monitoring proper configuration compliance, what is a business supposed to do? The small business can pick a simple tool, but an enterprise is left finding something that meets their unique needs. So, do they use different tools for different platforms? Deploy agents and entire infrastructure to support it? Or, use one tool that can serve multiple functions and platforms?

If you have read my blogs before, you will see that we promote using one tool for multiple functions within a business. Recently, with the release of Retina CS 2.1 and the Retina Network Security Scanner 5.12.0, we have begun to tackle the problem of configuration compliance on multiple platform platforms. Using OVAL as assessment language, eEye has expanded configuration compliance to Linux and has embarked on a strategic solution to support Unix and network devices all from one product. Vulnerability assessment and configuration compliance no longer need to be separate tools and no longer needs to be different products or agents depending on the platforms your business has selected to deploy and support.

In addition, eEye’s Configuration Compliance Add-On Module simplifies this process by shipping OVAL guidelines for  FDCC, NIST, Microsoft, USGCB, RHEL, and importing third party guidelines from organizations like CIS.  With all the templates directly in the solution, you’ll find it easier than ever to audit configuration settings against internal policies or external best practices, and to centralize reporting for monitoring and regulatory purposes. Below are some of the benefits of multiple platform configuration compliance within a vulnerability scanning solution:

  • Single console approach ensures a more stable and secure infrastructure, proactively reducing the risks of security breaches and lowering costs by enabling enterprise-wide management.
  • Configuration assessment for critical security settings that include audit settings, security settings, user rights, logging configuration, etc.
  • Streamlined reporting for government and corporate standards with built-in vulnerability reporting and integration with Retina Insight for delta dashboards and drilldowns.
  • Simple wizard for benchmark compliance leveraging a robust library of industry benchmarks encapsulating industry knowledge and experience.
  • Built-in templates for configuration compliance from FDCC, NIST, STIGS, USGCB, RHEL, and Microsoft.
  • OVAL 5.3 SCAP-certified scan engine and interpreter and OVAL 5.8 compatible for additional platform support.

Please contact us for more information on how your organization can benefit from multiple platform configuration compliance. eEye is pioneering the next-generation Unified Vulnerability Management solution and supporting a full- function, multi-platform configuration compliance engine and vulnerability assessment solution in one product. eEye believes in simplifying vulnerability management.

Leave a Reply

Additional articles

How To Implement The Australian Signals Directorate’s Top 4 Strategies

Posted October 20, 2014    Morey Haber

The Australian Signals Directorate (ASD), also known as the Defence Signals Directorate, has developed a list of strategies to mitigate targeted cyber intrusions. The recommended strategies were developed through ASD’s extensive experience in operational cyber security, including responding to serious security intrusions and performing vulnerability assessments and penetration testing for Australian government agencies. These recommendations…

Tags:
, , , ,
asp-mvc

Exploiting MS14-059 because sometimes XSS is fun, sometimes…

Posted October 17, 2014    BeyondTrust Research Team

This October, Microsoft has provided a security update for System.Web.Mvc.dll which addresses a ‘Security Feature Bypass’. The vulnerability itself is in ASP.NET MVC technology and given its wide adoption we thought we would take a closer look. Referring to the bulletin we can glean a few useful pieces of information: “A cross-site scripting (XSS) vulnerability exists…

Tags:
4bestpracticesaudits-blog

Four Best Practices for Passing Privileged Account Audits

Posted October 16, 2014    Chris Burd

Like most IT organizations, your team may periodically face the “dreaded” task of being audited. Your process for delegating privileged access to desktops, servers, and infrastructure devices is a massive target for the auditor’s microscope. An audit’s findings can have significant implications on technology and business strategy, so it’s critical to make sure you’re prepared…

Tags:
, , , ,