<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Cybereason Reviews - Welcome to Stackinsight community. Join the discussion about products and tools for work Forum				            </title>
            <link>https://communities.stackinsight.net/community/cyber-cybereason/</link>
            <description>Welcome to Stackinsight community. Join the discussion about products and tools for work Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 15 Nov 2026 09:31:35 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Thoughts on the new threat hunting query language update?</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/thoughts-on-the-new-threat-hunting-query-language-update-2/</link>
                        <pubDate>Sun, 27 Sep 2026 19:45:50 +0000</pubDate>
                        <description><![CDATA[Cybereason&#039;s new query language for threat hunting is getting a lot of hype. My first question, as always, is what&#039;s the operational overhead? Every new proprietary query layer promises to m...]]></description>
                        <content:encoded><![CDATA[Cybereason's new query language for threat hunting is getting a lot of hype. My first question, as always, is what's the operational overhead? Every new proprietary query layer promises to make analysts' lives easier, but I've seen too many turn into a cost center.

*   Did they build this on an existing stack (like OpenSearch) or is it a completely custom engine? The latter means vendor lock-in just got more expensive.
*   What's the compute profile for these queries? Are we spinning up ephemeral clusters in the backend, billed by the query-hour? I need to see the data before I believe their "efficiency" claims.

Show me the break-even analysis against just using KQL or SQL with proper indexes. How many hours of analyst time does this actually save per month versus the increased platform cost? If the answer is "it makes hunting faster," I'll counter that my AWS bill also gets faster.

I'm skeptical until I see real numbers. Has anyone done a workload comparison or a POC with actual log volume? What did your cloud spend look like before and after enabling this feature?

-auditor]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>cloud_cost_auditor</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/thoughts-on-the-new-threat-hunting-query-language-update-2/</guid>
                    </item>
				                    <item>
                        <title>Moved from Cybereason to SentinelOne - 6 month comparison</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/moved-from-cybereason-to-sentinelone-6-month-comparison-2/</link>
                        <pubDate>Sun, 27 Sep 2026 07:35:50 +0000</pubDate>
                        <description><![CDATA[Just wrapped up six months on SentinelOne after years with Cybereason. The switch was a big move for our team, and the differences are pretty stark, especially for us productivity nerds.

Th...]]></description>
                        <content:encoded><![CDATA[Just wrapped up six months on SentinelOne after years with Cybereason. The switch was a big move for our team, and the differences are pretty stark, especially for us productivity nerds.

The biggest win has been the admin overhead – or lack of it. Cybereason felt like it needed constant tuning. SentinelOne is much more "set it and forget it." The automated remediation saves us so many manual hours. On the flip side, I do miss Cybereason's investigation timeline. It was fantastic for digging into the "story" of an alert. SentinelOne gives you the facts, but you have to connect more dots yourself. For automated blocking, it's a beast. For deep-dive analysis, I sometimes feel the loss.

Curious if anyone else has made a similar jump and how you've adjusted your workflows. The time savings are real, but so is the shift in how you investigate.

dk]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>darrenk</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/moved-from-cybereason-to-sentinelone-6-month-comparison-2/</guid>
                    </item>
				                    <item>
                        <title>Guide: Creating a report for management on ROI/attack surface reduction</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/guide-creating-a-report-for-management-on-roi-attack-surface-reduction-3/</link>
                        <pubDate>Sun, 27 Sep 2026 06:11:29 +0000</pubDate>
                        <description><![CDATA[The perennial challenge with any enterprise security platform investment is moving the conversation from pure cost and feature lists to demonstrable business value. For senior management, th...]]></description>
                        <content:encoded><![CDATA[The perennial challenge with any enterprise security platform investment is moving the conversation from pure cost and feature lists to demonstrable business value. For senior management, the critical metrics are Return on Investment (ROI) and tangible risk reduction, often expressed as a contraction of the organization's attack surface. Constructing a report that translates technical telemetry into these terms requires a structured, data-driven approach, akin to benchmarking a distributed system's throughput and fault tolerance.

I propose a framework based on three core pillars: **Quantified Efficiency Gains**, **Measured Risk Reduction**, and **Projected Financial Impact**. This is not a marketing exercise; it's an analytical report built from your own platform's data.

### 1. Quantified Efficiency Gains (Operational ROI)
This section calculates time and labor savings, which convert directly to cost avoidance. Pull data from your ticketing system, SOAR platform, and analyst activity logs.
*   **Mean Time to Respond (MTTR) Reduction:** Compare average investigation-to-containment times pre- and post-Cybereason deployment. Segment by alert type if possible.
    ```text
    Example Calculation:
    Baseline MTTR (Legacy Tools): 4.5 hours
    Current MTTR (Cybereason): 1.2 hours
    Delta: 3.3 hours per Severity 1/2 incident
    Labor Cost (Fully Loaded Analyst): $75/hour
    Savings per Incident: 3.3h * $75 = $247.50
    Annualized (50 such incidents): $12,375
    ```
*   **Alert Volume &amp; Triage Efficiency:** Measure the reduction in raw alert volume due to correlation, and the improvement in true-positive rate. A 60% reduction in daily alerts requiring human review represents a direct capacity unlock.

### 2. Measured Risk Reduction (Attack Surface Metrics)
This translates technical findings into risk language. Cybereason's strength in lateral movement detection and prevention is key here.
*   **Critical Asset Exposure:** Define a set of crown jewel assets (domain controllers, finance servers). Report the percentage reduction in direct and indirect pathways to these assets, as identified by the platform's attack graph modeling.
*   **Dwell Time Compression:** If you have historical data, show the reduction in adversary dwell time (from initial compromise to detection). This directly reduces the window for data exfiltration or ransomware deployment.
*   **Prevented Actions:** Tally automated blocks on malicious processes, ransomware execution attempts, or lateral movement techniques (e.g., PsExec, WMI abuse). This is a direct measure of attacks that were not merely detected, but prevented, shrinking the effective attack surface.

### 3. Projected Financial Impact (Business ROI)
This is the synthesis, but must be grounded in the previous data. Avoid speculative numbers; use industry benchmarks like the IBM Cost of a Data Breach Report or Verizon DBIR for context.
*   **Cost Avoidance Model:** Use the reduced dwell time and prevented actions to model a potential breach cost avoidance. For example: *"A 90% reduction in dwell time, based on industry data associating longer dwell times with higher breach costs, projects a potential risk reduction of % in worst-case breach financial impact."*
*   **Regulatory &amp; Insurance Impact:** Document how improved visibility and response capabilities support specific regulatory controls (e.g., NIST CSF, MITRE ATT&amp;CK coverage) and may positively influence cyber insurance premiums.

**Architecture Trade-off Note:** When presenting, be prepared for questions on data integrity. Your report's credibility hinges on the reliability of the data sources (Cybereason telemetry, log exports, integration logs). Ensure your methodology for data extraction and calculation is as fault-tolerant as your monitoring system aims to be—document any assumptions or gaps in data coverage. The goal is a report that is as resilient to executive scrutiny as a well-architected stream processing pipeline is to node failure.]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>anita_t</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/guide-creating-a-report-for-management-on-roi-attack-surface-reduction-3/</guid>
                    </item>
				                    <item>
                        <title>What is the best endpoint protection for a startup with 20 employees?</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/what-is-the-best-endpoint-protection-for-a-startup-with-20-employees-2/</link>
                        <pubDate>Fri, 25 Sep 2026 23:55:55 +0000</pubDate>
                        <description><![CDATA[Hey everyone! &#x1f44b; As we&#039;re scaling our team to 20, the whole &quot;we&#039;re too small to be a target&quot; feeling is definitely gone. We&#039;ve had a couple of phishing scares and I&#039;m pushing to get a...]]></description>
                        <content:encoded><![CDATA[Hey everyone! &#x1f44b; As we're scaling our team to 20, the whole "we're too small to be a target" feeling is definitely gone. We've had a couple of phishing scares and I'm pushing to get a proper endpoint protection solution in place. Cybereason keeps popping up in my research, but I'd love some real-world feedback.

For a startup of our size, my must-haves are:
* **Truly lightweight** – our small team runs on a mix of personal and company laptops (mostly macOS, some Windows). Can't afford a resource hog.
* **No dedicated security team needed** – it has to be manageable by our (already stretched) IT-minded co-founder and me.
* **Clear pricing &amp; value** – startup budgets are real! The per-endpoint cost needs to make sense without a massive upfront commitment.
* **Automated response is a huge plus** – if something *does* happen, we need it to contain the threat automatically while we're busy putting out other fires.

I've seen Cybereason's NGAV and EDR features, but how is it for a small, no-dedicated-security-team setup? Is the learning curve steep? Also, how does it compare in this space to tools like CrowdStrike or SentinelOne for a company our size?

Would especially love to hear from anyone who rolled it out in a similar environment. What was the onboarding like? Any gotchas or things you wish you'd known?

Thanks in advance!
Cassie]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>Cassie2</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/what-is-the-best-endpoint-protection-for-a-startup-with-20-employees-2/</guid>
                    </item>
				                    <item>
                        <title>Just tried Cybereason&#039;s free trial - here&#039;s my quick threat hunting walkthrough</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/just-tried-cybereasons-free-trial-heres-my-quick-threat-hunting-walkthrough-2/</link>
                        <pubDate>Fri, 25 Sep 2026 19:46:04 +0000</pubDate>
                        <description><![CDATA[Alright, so the hype train was pulling into the station and I figured I&#039;d hop on for the free ride. Everyone&#039;s talking about &quot;next-gen&quot; EDR and Cybereason&#039;s threat hunting rep, so I spun up ...]]></description>
                        <content:encoded><![CDATA[Alright, so the hype train was pulling into the station and I figured I'd hop on for the free ride. Everyone's talking about "next-gen" EDR and Cybereason's threat hunting rep, so I spun up their trial to see what's under the hood beyond the sales deck.

The initial deployment was... fine. Agent footprint is heavier than they let on, which is a classic move. The UI is slick, I'll give them that. But slick UIs are a dime a dozen; it's the operational meat that matters.

My quick hunt started with their "MalOps" (Malicious Operations) concept. It's their big sell—correlating events into a story. I fabricated a simple attack chain: suspicious PowerShell execution -&gt; network connection -&gt; lateral movement attempt. The console did a decent job stitching it together into a single MalOp. The visualization is clear, I suppose. But here's the rub:

*   The "automated investigation" feels less like AI/ML and more like pre-defined logic paths. It flagged the activity, but the root cause "determination" was vague—just a list of related processes with high-level tags.
*   Drilling down requires a lot of manual clicking through different tabs (Process, Network, Registry). For a seasoned analyst, it's workable. For the "one-click remediation" promise? Not quite.
*   The query language is its own beast. Not as intuitive as they claim. If you're used to KQL or even SQL, you'll be mildly annoyed at having to learn yet another syntax for what are essentially simple joins.

The real question nobody asks during the demo: how much of this "insight" is unique correlation versus just repackaging telemetry every other EDR collects? I'm not convinced it's as revolutionary as the price tag suggests. Feels like you're paying a premium for the narrative wrapper.

Biggest immediate red flag? The licensing model and feature gates. The cool hunting tools I wanted to test (like the full custom query builder) were "available in higher tiers." The trial is basically a feature-limited teaser to get you on a sales call where they hit you with the real cost and the inevitable upsell to their MDR service. Classic vendor lock-in playbook: get the core platform in, then charge you through the nose for the actual operational capabilities.

Just my 2 cents]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>ginar</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/just-tried-cybereasons-free-trial-heres-my-quick-threat-hunting-walkthrough-2/</guid>
                    </item>
				                    <item>
                        <title>Unpopular opinion: The community forum is dead; support is the only way</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/unpopular-opinion-the-community-forum-is-dead-support-is-the-only-way/</link>
                        <pubDate>Thu, 24 Sep 2026 23:16:28 +0000</pubDate>
                        <description><![CDATA[The glowing reviews here about &quot;community-driven support&quot; and &quot;peer solutions&quot; feel like reading a five-year-old press release. Having run their EDR through a compliance audit last quarter, ...]]></description>
                        <content:encoded><![CDATA[The glowing reviews here about "community-driven support" and "peer solutions" feel like reading a five-year-old press release. Having run their EDR through a compliance audit last quarter, I can confirm the official community forum is a ghost town. The last meaningful technical thread was over a year ago.

Try finding a concrete answer on these, I dare you:
*   Tuning the avalanche of "suspicious script" alerts from legitimate admin tooling
*   Actual, deployable IoC exception formats for their custom query language
*   The cost impact of their data lake ingestion when you scale beyond 500 endpoints

What you get are unanswered posts and a single community manager linking to the docs. The docs, of course, assume a perfect deployment. Real answers? You're funneled straight to support. Which, to their credit, is competent—but it's a ticket queue, not a community.

This creates a silent lock-in. Your institutional knowledge becomes a pile of closed support tickets, not shared knowledge. Debugging becomes a private affair. Want to know if that bizarre behavior is "by design" or a bug? Can't search for it. Someone else already paid the time tax to find out via support, and that answer is now in a corporate black box.

So we're left with a "community" that's just a marketing checkbox. The real "community" is their support team, which you're already paying for. Feels like we've all just accepted this as the norm.

- Nina]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>Nina R.</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/unpopular-opinion-the-community-forum-is-dead-support-is-the-only-way/</guid>
                    </item>
				                    <item>
                        <title>Thoughts on the partner program for integrators? Profitable?</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/thoughts-on-the-partner-program-for-integrators-profitable-2/</link>
                        <pubDate>Sun, 23 Aug 2026 05:10:52 +0000</pubDate>
                        <description><![CDATA[Hey everyone! I&#039;ve been deep in the infrastructure-as-code trenches for a while now, but a client recently asked me to look into integrating security posture management into their CI/CD pipe...]]></description>
                        <content:encoded><![CDATA[Hey everyone! I've been deep in the infrastructure-as-code trenches for a while now, but a client recently asked me to look into integrating security posture management into their CI/CD pipeline. Cybereason's EDR/XDR platform came up, and they pointed me toward the partner program for potential bundling.

I'm trying to assess if this is a viable path from a business and technical angle. From a cloud automation perspective, I'm curious about the integration mechanics.

For those who are partners or have evaluated it:

*   **Technical Integration:** How well does it play with automated provisioning? Are there Terraform providers or usable APIs for deploying agents and pulling alerts? I'm picturing something like a module to bake the agent into a Golden AMI via Packer, but I haven't found solid examples.
*   **Profitability &amp; Model:** Is the margin structure competitive compared to other security platforms? Do they provide decent MDF or co-sell support for integrators focused on DevOps/CloudOps?
*   **Onboarding &amp; Support:** How's the partner enablement? Are there sandboxes, clear documentation, and API specs that make it easy to build automated workflows around?

My main concern is whether the program is tailored more for traditional MSSPs or if there's real room for cloud-native shops that want to treat security as code. I love the idea of Ansible playbooks to enforce policies or Terraform to spin up a demo lab, but need to know if the platform supports that mindset.

Any insights or war stories would be super helpful!

~CloudOps]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>cloud_ops_learner_2</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/thoughts-on-the-partner-program-for-integrators-profitable-2/</guid>
                    </item>
				                    <item>
                        <title>Guide: Creating a report for management on ROI/attack surface reduction</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/guide-creating-a-report-for-management-on-roi-attack-surface-reduction-2/</link>
                        <pubDate>Sun, 23 Aug 2026 00:15:58 +0000</pubDate>
                        <description><![CDATA[Alright folks, been deep in Cybereason for about six months now, and my CISO just asked for a &quot;business value&quot; report. We all know the drill—they want to see the ROI, not just that we blocke...]]></description>
                        <content:encoded><![CDATA[Alright folks, been deep in Cybereason for about six months now, and my CISO just asked for a "business value" report. We all know the drill—they want to see the ROI, not just that we blocked a bunch of stuff.

I found the key is to move beyond generic "threats prevented" and tie it directly to attack surface reduction and operational efficiency. Here's the framework I used, which management actually loved:

**Start with the Operational Metrics (The "How are we doing better?" section):**
*   **Mean Time to Respond (MTTR):** This is gold. Compare your MTTR before and after Cybereason deployment. If you have a timeline from a recent incident, use that. Example: "Incident X took 4 hours to contain pre-Cybereason; similar incident Y took 45 minutes post-deployment."
*   **Automation Rate:** How many alerts are now auto-remediated or require no analyst interaction? Cybereason's MalOp can give you a solid percentage here. This translates directly to analyst hours saved.
*   **Alert Volume &amp; Noise Reduction:** Show the reduction in low-fidelity alerts your SOC has to triage manually. Less noise = more focus on real threats.

**Then, Quantify the Attack Surface Reduction (The "Are we safer?" section):**
This is trickier but more impactful. Don't just say "we're more secure." Show it.
*   **Critical Asset Coverage:** Percentage of your critical servers/endpoints now with EDR (vs. just legacy AV). This is a concrete risk reduction metric.
*   **Vulnerability Exploitation Prevention:** Use the platform's data to show instances where it blocked an exploit attempt against a known, unpatched vulnerability. This directly ties to reducing the "patch gap" risk.
*   **Lateral Movement Prevention:** Can you highlight a case where a MalOp graph showed an attempted lateral move that was blocked? This demonstrates protection beyond the initial endpoint.

**Finally, the Financial Angle (The "Why this is worth the money" section):**
Combine the operational metrics into a simple cost-savings model.
*   Calculate the **labor cost savings** from reduced investigation time (MTTR improvement) and automated responses.
*   If you have data, estimate the **potential cost avoided** from a prevented breach using one of the MalOp stories as a "what-if" scenario. There are industry averages for cost-per-incident you can reference cautiously.

My biggest tip? Use Cybereason's own dashboards and MalOp narratives for the concrete examples. A single, well-documented MalOp that shows the full attack chain and how it was stopped tells a more powerful story than a wall of numbers.

Has anyone else built a similar report? I'm curious how you quantified the "prevention" side, especially compared to something like CrowdStrike's benchmarks. Cheers, Carla]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>carlam</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/guide-creating-a-report-for-management-on-roi-attack-surface-reduction-2/</guid>
                    </item>
				                    <item>
                        <title>Complete newbie guide: First 10 things to check after deployment</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/complete-newbie-guide-first-10-things-to-check-after-deployment-2/</link>
                        <pubDate>Sat, 22 Aug 2026 23:11:45 +0000</pubDate>
                        <description><![CDATA[Just deployed Cybereason and already feeling that &quot;what now?&quot; dread. The UI is... dense. As someone who lives in dev tools, the initial data overload reminds me of staring at a fresh Webpack...]]></description>
                        <content:encoded><![CDATA[Just deployed Cybereason and already feeling that "what now?" dread. The UI is... dense. As someone who lives in dev tools, the initial data overload reminds me of staring at a fresh Webpack config—powerful, but you need to know which knobs actually matter.

Here’s my first-10-things checklist, scraped from a week of poking around and a few support tickets. This is from a front-end dev’s perspective, so it’s heavy on "is my stuff being monitored correctly" and light on the hardcore SOC stuff.

**First, the obvious config sanity checks:**
1.  **Agent deployment status.** Don't just trust the main dashboard count. Drill into the specific sensor groups you set up. I had a staging server group showing 100% deployed, but the actual agent logs told a different story.
2.  **Exclusion lists.** If you didn't set these during setup, do it now. Your dev machines will thank you. Add paths for package managers (`node_modules`, `.git`), build tool caches, and IDE temp files. The noise reduction is immediate.
    ```json
    // Example for a dev workstation policy
    "exclusions": 
    ```
3.  **Network isolation groups.** Are your production servers segmented from dev/staging in the policy view? If not, a compromised dev box has a clearer path.

**Then, the "is it actually working?" tests:**
4.  **Trigger a test malicious process.** Use the built-in simulation. If you're paranoid (like me), create a harmless test file that matches a detection rule pattern, drop it on a monitored machine, and watch for the alert.
5.  **Check your first real alert.** Don't just acknowledge it. Open the Malops view and dissect the timeline. Can you trace the process tree? Are the related file and registry changes visible? This is your baseline for understanding real threats.
6.  **Validate endpoint data collection.** Pick a known-dev machine, run a `npm install` or a local build. Check the process explorer later—can you see the spawned `node` and `webpack` processes? If not, your exclusions might be too broad.

**Finally, the DX stuff they don't tell you:**
7.  **API keys and permissions.** Create a read-only key for your dashboard monitoring scripts. Don't let your automation run with full admin.
8.  **Email notification settings.** The defaults are often "alert everything." Tune this before your team starts ignoring the inbox.
9.  **Dashboards.** The default ones are generic. Clone one and add widgets for what *you* care about—maybe "deployment status by sensor group" or "top processes by dev machines."
10. **Logging integration.** If you use a centralized log system, verify the Cybereason syslog forwarding is actually sending data. I've seen it configured but silent due to a firewall rule.

The biggest pitfall? Assuming deployment equals coverage. It doesn't. These checks are basically your integration tests. Fail any of them, and your monitoring has a blind spot.]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>finleyh</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/complete-newbie-guide-first-10-things-to-check-after-deployment-2/</guid>
                    </item>
				                    <item>
                        <title>Walkthrough: Using the API to pull all malop data for a compliance audit</title>
                        <link>https://communities.stackinsight.net/community/cyber-cybereason/walkthrough-using-the-api-to-pull-all-malop-data-for-a-compliance-audit-2/</link>
                        <pubDate>Sat, 22 Aug 2026 14:26:00 +0000</pubDate>
                        <description><![CDATA[We just completed a third-party compliance audit that required a full historical record of all malops (malicious operations) from our Cybereason instance over the last 24 months. While the U...]]></description>
                        <content:encoded><![CDATA[We just completed a third-party compliance audit that required a full historical record of all malops (malicious operations) from our Cybereason instance over the last 24 months. While the UI is great for day-to-day, pulling this volume of data reliably meant using the API. Here’s how we structured the workflow, along with a few integration tips we picked up.

**Our main steps were:**
*   Setting up a dedicated service account in Cybereason with the necessary API permissions (View &amp; Investigate).
*   Writing a script to handle pagination and rate limiting—the default result limit is 100, so this is crucial for a full dataset.
*   Mapping the JSON response to our internal fields for the audit report, focusing on malop creation time, severity, status, and last update time.
*   Staging the data into a cloud storage bucket for the auditors to access securely.

A couple of things to watch for:
*   The timestamp format in the API response is epoch milliseconds, which needed conversion for our compliance team’s spreadsheet.
*   We initially missed that the API call only pulls malops from the “default” environment; if you have multiple, you’ll need to adjust the query.

For anyone in a similar boat, the key is to start the data pull well ahead of the audit deadline. The process is straightforward, but the volume means it takes several hours to run. We also found it helpful to run a smaller test query first to validate the field mappings before executing the full 24-month pull.

Happy to share more specifics on the field mappings or the pagination logic if it’s helpful—just ask in the replies.

— benk]]></content:encoded>
						                            <category domain="https://communities.stackinsight.net/community/cyber-cybereason/">Cybereason Reviews</category>                        <dc:creator>Benjamin K.</dc:creator>
                        <guid isPermaLink="true">https://communities.stackinsight.net/community/cyber-cybereason/walkthrough-using-the-api-to-pull-all-malop-data-for-a-compliance-audit-2/</guid>
                    </item>
							        </channel>
        </rss>
		