Skip to content

FILE IMPORT · OVERVIEW DROPPOINT

Your CSV and JSON exports become indicators. You drop, we import.

A scanner that only produces reports, a console that exports to CSV, an isolated site: the data already exists. DropPoint is an S3-compatible file drop-off reserved for your organization, with one space per tool. Push your exports by hand or from a scheduled script, and OverView imports them on the next synchronization.

YOUR TOOLSSentinelOneagents.csvvCentervms.jsonNessusscan.csvCSV / JSON EXPORTSCHEDULED SCRIPT$ aws s3 sync exports/ s3://sentinelone/HTTPSSigV4s3.oversoc.comONE SPACE PER TOOLsentinelonevmwarenessusOverView98 %EDR1 204ASSETS37HIGHIMPORTED ON NEXT SYNC
  • HTTPS and S3 v4 signature on every request
  • A drop-off space isolated per organization
  • Credentials revocable at any time
  • Why it is safe ↓

WHAT CHANGES

0network flow to open: you push, we read
1 scripton a schedule is enough (cron, launchd, Task Scheduler)
CSV · JSONthe exports your tools already produce
60+connectors accept file mode

THEY DID IT

The City of Lille consolidated 10 tools and 5,000 devices, through APIs or flat files

After the 2023 cyberattack and under NIS 2 pressure, the City of Lille, Lomme and Hellemmes chose to build on what it had: AD, ITSM, MDM, EDR, scanners and CMDB were collected automatically, through APIs or flat files, with no re-keying and no migration project.

Read the case study →
Jean-François Rosendo, IT Director — City of Lille, Lomme & Hellemmes

Jean-François Rosendo

IT Director — City of Lille, Lomme & Hellemmes

Ville de Lille

« What drew us in from the start wasn’t adding yet another security tool — we already had plenty. We were looking instead for the ability to federate the information we already had. The goal was simple: create a single source of truth. »

THE PROBLEM

Not all data comes through an API

1

Tools with no usable API

A scanner that only produces reports, a console that exports to CSV, a home-grown CMDB: the data exists, but no API lets you read it.

2

Networks you do not open

Sensitive sites, isolated environments, contractors: sometimes the only thing allowed out is a file.

3

Manual imports that do not last

Emailing an export every month works once. Then someone forgets, the format changes, and the indicator freezes.

HOW IT WORKS

One space per tool, one file per export

DropPoint speaks S3, the standard your scripts, backups and tools already know. No proprietary client to install, nothing for your security team to vet.

  1. 01

    Generate your credentials

    In OverView: Settings, Security, S3 Credentials. An Access Key / Secret Key pair scoped to your organization, revocable at any time.

  2. 02

    Pick your client

    AWS CLI, rclone, boto3, PowerShell, Cyberduck or WinSCP: any S3 client works. Point it at s3.oversoc.com.

  3. 03

    Drop your exports

    Each connector has its own space, an S3 bucket (sentinelone, vmware, azure…). Copy your CSV or JSON files to its root.

  4. 04

    OverView imports

    New files are detected and ingested on the next synchronization. Automate with cron, launchd or Windows Task Scheduler, and the indicator refreshes with every export.

WHICH ROUTE FOR WHICH TOOL

Three routes, one inventory

Cloud, on-prem, file: every source has a path into OverView. Most customers combine two of them.

Your situationRecommended route
SaaS tool with a public API (EDR, Entra ID, Intune, ServiceNow)Cloud API
Internal tool with an API (GLPI, vCenter, Active Directory, Nessus, Centreon)OverView OutPost
Several internal tools behind the same firewallOutPost, one VM for all of them
Tool with no API, or that only produces exports (scanner report, antivirus console, home-grown CMDB)OverView DropPoint
Isolated site or a network you do not openDropPoint, a file goes out, nothing comes in
Both cases in the same estateOutPost + DropPoint, same inventory
SECURITY

Isolated by design

Isolated per organization

Each organization has its own drop-off spaces (buckets). Your credentials only open your connectors’, nothing else.

Revocable credentials

The Secret Key is shown only at generation time. Disable or regenerate a key at any time from OverView.

S3 signature v4

Every request is signed. An unknown key, an invalid signature or the wrong bucket is rejected.

HTTPS only

TLS endpoint, no cleartext transfer. Exclude it from your outbound proxy’s SSL inspection, which would break the request signature.

No inbound flow

Your systems push to DropPoint. OverView never needs to reach your network.

Standard S3, nothing to qualify

You keep your usual tools, scripts and audit procedures. No proprietary OverView client for your security team to vet.

Recommended reading before your security review

HAND THIS TO YOUR ADMIN

Five lines to automate the first export

Paste this block into the ticket. The getting started guide ships ready-to-paste cron, launchd and PowerShell scripts.

  1. 01Create the credentials in OverView: Settings, Security, S3 Credentials (the Secret Key is shown only once)
  2. 02Configure an AWS CLI profile: endpoint https://s3.oversoc.com, path-style addressing, signature v4
  3. 03Export from the source tool to CSV or JSON into a dedicated local folder
  4. 04Schedule “aws s3 sync ./exports s3://<connector>/” with cron, launchd or Windows Task Scheduler
  5. 05Exclude s3.oversoc.com from the outbound proxy’s SSL inspection, and check the system clock (NTP)

TECH SHEET

What to know

Protocol
S3 API, AWS signature v4, path-style addressing
Endpoint
https://s3.oversoc.com
Formats
CSV, JSON
Size per request
500 MB, automatic multipart beyond with AWS CLI or rclone
Quota
No per-organization quota enforced today
Tested clients
AWS CLI v2.13+, AWS Tools for PowerShell, rclone, boto3, Cyberduck, WinSCP
Automation
cron, launchd, Windows Task Scheduler
Layout
One bucket per connector type, files at the root

WHAT YOU UNLOCK

Every connector has its drop-off space

All OverView connectors accept file mode. Export from your tool, drop it in the connector’s space, and indicators compute just like with an API.

SentinelOneSentinelOne
ESETESET
Kaspersky Security CenterKaspersky Security Center
VMware vCenterVMware vCenter
Azure Virtual MachinesAzure Virtual Machines
Google Cloud PlatformGoogle Cloud Platform
NutanixNutanix
Tenable NessusTenable Nessus
OpenVASOpenVAS
NmapNmap
Active DirectoryActive Directory
OCS InventoryOCS Inventory
iTopiTop
SCCM / MECMSCCM / MECM
WSUSWSUS
WAPTWAPT
VeeamVeeam
CentreonCentreon
SolarWindsSolarWinds

Examples of indicators unlocked

  • Antivirus coverage by device typeSources: ESET or Kaspersky console export
  • Obsolete servers with High vulnerabilitiesSources: Nessus or OpenVAS report
  • Patch status per deviceSources: SCCM or WSUS export
  • Share of VMs that are backed upSources: Veeam export
  • Devices seen on the network but missing from the CMDBSources: Nmap scan + CMDB export

FREQUENTLY ASKED

What your team will ask

No. Any standard S3 client works: AWS CLI, rclone, boto3, PowerShell, Cyberduck, WinSCP. Just point it at s3.oversoc.com with path-style addressing.

Ready to regain control?

Plug in your sources, see the value in 14 days. Free access, no commitment, 45-minute setup.

Try for free