Traceix Traceix
TRIAGE DROP ZONE

Make suspicious-file triage automatic. One folder. One pipeline. One dashboard.

Most teams don’t lose time on analysis — they lose time on intake. A Traceix Cortex Agent turns a folder into a drop zone so files land in one place and triage becomes a consistent, repeatable flow: classify, optionally enrich, then review decision-ready alerts.

Cleaner intake, fewer pings Standard outputs (alerts + JSON) Runbook-friendly workflow
Not an EDR. On purpose.
EDR is “monitor everything.” Cortex is “answer one question extremely well”: what is this file? No continuous endpoint telemetry. Just a clean intake lane that produces triage outcomes.
1) Build an agent
Pick classification + options.
2) Point at a folder
That folder becomes intake.
3) Review alerts
Triage without the chaos.
Fastest way to feel the value:
Build one agent → point it at a folder → drop one file in. When an alert appears without anyone uploading anything, it clicks.
What your team message looks like (operator-grade handoff)
Drop Zone: \\TRIAGE\DROP\INBOX (or C:\TriageDropZone\)
1) Put suspicious attachments/downloads in the Drop Zone
2) Check Traceix → Cortex Alerts for the triage result
3) If flagged: quarantine + escalate with the alert link + JSON export
Goal: the next person knows where to put files and where to look — instantly.
You can read this page without logging in. Login is only needed to build agents and view alerts.
What it looks like
Triage Drop Zone New files Traceix Classify Alert Actionable triage Dashboard
Output: alerts + JSON export
Purpose: standardized file intake
In one sentence: files go in one place, answers come out in one dashboard.
Start small: one agent + one folder. Add more Drop Zones later by workflow or team.

Why a Triage Drop Zone matters

Manual uploads work — until the day they don’t. Someone forgets. Someone can’t find the file. Someone sends it in chat. A Drop Zone removes the decision and standardizes intake: one place files land, one place results appear.

Stop the intake chaos
No more “send it to me,” “upload it here,” “where did that go?” The folder is the contract.
Make triage predictable
Same pipeline, same outputs, every time — easy to train, easy to operate.
Move decisions faster
Intake → alert → action. Less coordination overhead, more actual work.
High-trust teams standardize intake
When intake is repeatable, triage becomes runbook-friendly: clearer handoffs, fewer interruptions, cleaner outcomes.
A real Drop Zone

Your folder is the contract: anything that lands there gets triaged automatically. Attachments, downloads, user-submitted samples — doesn’t matter.

Fast + consistent

Classification first, then optional enrichment (metadata, CAPA, YARA) based on your agent config.

Decision-ready alerts

Results become alerts in Traceix so you can filter, export JSON, mark reviewed, and move on.

Not an EDR. A triage automation pipeline.

If you need fleet-wide behavior telemetry and continuous monitoring — that’s EDR. Cortex Agents are for file intake triage: one Drop Zone, consistent processing, and a dashboard decision.

Quick comparison
EDR vs manual submissions vs Cortex Agents (Triage Drop Zone).
Capability EDR
Continuous telemetry
Sandboxes
One-off submissions
Cortex Agents
Triage Drop Zone
Continuous monitoring Yes — always on
Endpoint telemetry
No
Submission-based
No — intentionally
Focused on intake + triage outcomes
File intake standardization Depends on rollout
Policy heavy
Manual upload
Works, but it’s a step
Strong — one folder becomes “the intake”
Drop → auto-submit → alert
Fast classification + alerts Possible, can be noisy
Telemetry mixed in
Yes — per submission
Not intake automation
Yes — automated + dashboard
Designed for “what is this file?”
Install on every endpoint? Typically, yes
For coverage
Not needed
Upload from anywhere
Not needed — one agent, one Drop Zone
Centralize intake without fleet rollout
Cost / complexity Higher
Deployment + tuning
Medium
Manual flow
Lower
Lightweight intake lane + alerts
Interpretation: Cortex Agents standardize file intake and produce consistent triage outcomes you can operate.
What Cortex Agents do NOT do
  • Continuous endpoint monitoring
  • Process & memory telemetry collection
  • Isolation / containment controls
  • “Install on every machine” surveillance
What Cortex Agents DO
  • Watch a dedicated folder for new files
  • Submit files to Traceix automatically
  • Return classification + optional enrichment
  • Create dashboard alerts you can act on
Bottom line: Cortex Agents make file triage fast, consistent, and easy to operate — without watching everything.

How Cortex Agents work

Intake → triage → dashboard decision. One flow your team can actually standardize.

  1. Step 1
    Create an agent

    Choose your pipeline: classification-only, or add enrichment (metadata / CAPA / YARA).

  2. Step 2
    Point it at a folder

    Install once on a workstation or server and set your dedicated intake path.

  3. Step 3
    Drop files in

    Attachments, downloads, “can you check this?” samples — anything needing an answer goes into the Drop Zone.

  4. Step 4
    Review alerts

    Filter, export JSON, mark reviewed, and move on with confidence.

Pro tip: Use a dedicated folder like C:\TriageDropZone\ or /home/user/triage-drop-zone. Don’t watch system/root directories (too many files → noise).

Who Cortex Agents are for

Anyone who needs a fast, repeatable answer to “what is this file?” before opening it, forwarding it, or running it.

“Check before I click” users

Downloads, attachments, client files — drop it in, get an answer.

SOC / Tier-1 triage

First-pass intake lane that turns file questions into alerts.

MSSPs

Standardize customer intake without “send me the file” chaos.

IR / DFIR intake

Build an evidence intake station that produces a clean review trail.

Teachers

Teach safe triage discipline using one shared Drop Zone + dashboard.

Students

Practice intake habits without building a heavy lab stack.

The point: You don’t need fleet-wide surveillance to standardize file triage. One Drop Zone gives you a repeatable intake path — and a dashboard to act on results.

Common use cases

  • Email attachment triage
  • User-reported “is this safe?” intake
  • Suspicious download quarantine folder
  • SOC first-line triage lane
  • MSSP customer intake Drop Zones
  • Teaching + training labs
  • IR/DFIR evidence intake station
  • Separate lanes by workflow/team

FAQ

Is this an EDR?

No. Cortex Agents don’t continuously monitor processes, memory, or your entire endpoint. They are a file triage automation pipeline.

What exactly is a “Triage Drop Zone”?

A dedicated folder that becomes your suspicious-file intake lane. Anything dropped into it is submitted automatically and becomes an alert you can review.

Is this only for big security teams?

No. One agent + one folder is enough for a solo user. Teams add more Drop Zones later for separate workflows.

What do I get back?

A classification result plus optional enrichment (metadata, CAPA, YARA) based on your configuration, and an alert in your dashboard you can filter and export as JSON.

Build your Triage Drop Zone
Create an agent, point it at a folder, and turn “what is this file?” into a consistent workflow.
Want the “ohhh” moment?
Build an agent → point at a folder → drop one file → see an alert appear.