Skip to content

Red-Team / Pentesting Guidance for Customers and their suppliers

SenseOn welcomes security tests, assessments, red team assessments and penetration tests of the SenseOn product by customers or by their suppliers. These activities are part of the wider security posture of a customer.

This page gives useful information for Red-Team assessments and pentest activities. In this documentation, the word 'testing' refers to all of these activities.


Details to provide to SenseOn in advance of testing:

  • The company that does the testing, and a contact for the testing
    • We can set up a call about the testing, or get more details. For example, we can get the account names and devices that you expect to use in the testing. We will use these details to correlate and report on all pentest activities.
  • What SenseOn must do with Alerts that occur during the testing. For example, escalate as usual, or close with 'Benign True Positive'.
  • Note: SenseOn and the customer agree the log retention as a commercial service level, and SenseOn configures it. Usually, the log retention is 30 days. With our LTTR service, it can be 90 days or more. To correctly correlate and report on any pentest, SenseOn must be able to search logs in this timeframe. The earlier we know about the testing (preferably in advance), the better we can start to report on it.

Configuration which may affect testing / response

  • If SenseOn runs as a detection platform together with another product, the customer usually runs SenseOn in 'Compatibility Mode'. This mode prevents conflicts with the other EDR. In this mode, SenseOn will Alert (but not Block) when it detects applicable test tools or techniques.

Scoping

  • SenseOn core endpoint, which runs on Windows, macOS, and Linux.
  • Data from Integrations.
  • Network telemetry from endpoints and network probes.
  • Some customers have our 'Managed SOC' service. With this service, our SOC analysts triage Cases (High priority and above only).
  • Log ingestion is available, but the SenseOn Managed SOC analytics are specific to each customer. The SOC can do a review, but it is possible that the review is not in depth. This depends on the volume.
  • Out-of-scope activities (SenseOn did not design the agent to detect these activities):
  • Ingestion of non-SenseOn host-based logs, for example Syslog
  • Misconfigurations in Active Directory
  • Web App penetration tests
  • Host network activity over HTTPS, for example Web Application scans and tests

Reporting

  • SenseOn will compare the techniques of the testers with the Cases that the SenseOn Platform created. SenseOn does this during and after the testing.
  • We will then do a 'gap analysis'. This analysis shows where we can improve our Detections, and where they worked well.
  • We will give this analysis to the customer in a report after the testing. The customer can use the report to show the effectiveness of the detections and service of SenseOn.