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.

Generic Third Party Integration

Posted May 24, 2011    Morey Haber

There is an inherent value to vulnerability assessment and attack data beyond the security team. Making relevant data available to other solutions, departments, and team members can streamline the vulnerability management process and ensure the workflow is seamless between departments and management. In addition, having tight data integration makes it easier to document workflow processes required by most regulatory compliance initiatives. Take for example this simple diagram for Retina CS and a generic integration into the Windows Application Log.

Critical events can be filtered as they entered into the management console and forwarded to the Application Log. Any third party event log watcher can trigger from these events to perform addition actions or notify appropriate individuals. This simple process can be documented as follows:

  • Perform periodic vulnerability scans
  • Set a threshold for events to be replicated into the Windows Application Log
  • Have Log Management System “x” or Network Management System “y” monitor for these events
  • Perform an automated rule when these are detected. For example, open a help desk tick after correlating the data with a CMDB, send an alert to the system owner outside of the security department, or perform an automated action.
  • This type of generic integration can be used to tie virtually any system to eEye’s solutions and raise the value of the data being collected without the need for any custom code. In addition, eEye supports the following generic integration points into each of our solutions.

    Based on these, a client can do everything from custom control of the scan engine to direct access of the data warehouse and integrated alerting functions. Some custom integrations that have been performed by our clients include:

  • Extraction of data for companywide ticketing system using XML.
  • Export of results for supplemental information to an enterprise level asset inventory system.
  • Security notification of rogue devices and any other detected anomaly including new ports being opened, etc.
  • Custom web pages hosting resulting data including SharePoint
  • Allow users to initiate their own scans and view results.
  • To that end, eEye has embarked on an aggressive third party integration program (with our partners) the following out of the box integrations that go far beyond basic event log scraping.

    These solutions work seamlessly with eEye to raise the awareness of vulnerability assessment data and provide a streamlined workflow for your business requirements. For more information regarding eEye and our third party integrations, please click here.

    Additional articles

    Cavalancia-Headshot - Medium

    Protecting Privileged Passwords: a “Past the Password” Perspective

    Posted July 6, 2015    Nick Cavalancia

    Webinar discussing the realities of today’s state of security using some of the most recent (and respected) reports in the industry, and look at what steps you should be taking to properly protect your privileged passwords.

    Tags:
    ,
    webinar 2

    On Demand Webinar: Because Auditing Stinks Sometimes

    Posted July 2, 2015    Lindsay Marsh

    Auditing stinks. Well, mostly stinks. In this on demand webinar, lead by Group Policy MVP Jeremy Moskowitz, you’ll learn the three key tenets to real Group Policy auditing. Tenet 1: Why do you care about Group Policy auditing? Tenet 2: How does Eventing help you know “Who did what?” Tenet 3: How does Reporting tell…

    Tags:
    , , , ,
    skeletonkey3_713678_713680

    Stopping the Skeleton Key Trojan

    Posted June 29, 2015    Robert Auch

    Earlier this year Dell’s SecureWorks published an analysis of a malware they named “Skeleton Key”. This malware bypasses authentication for Active Directory users who have single-factor (password only) authentication. The “Skeleton Key” attack as documented by the SecureWorks CTU relies on several critical parts.

    Tags:
    , , , , ,