For MSSPs who serve many clients
One tenant per client
Each client is its own tenant, all on one console, so the answer comes from how the platform is built.
The cost of a console per client
Separate consoles, logins and reports consume time the team could spend on client security.
On one console, each new client adds billable work without adding another system to run.
Tenant separation and access records
Each tenant has its own users, data sources, policies and reports, all on one console.
The console records every login and search, so the provider can show a client who looked at its data.
Onboarding one client at a time
A credential vault tests each connection before saving it, so a new tenant starts with tested sources.
Later clients use the same administration tools, while keeping their own policies and records.
Questions about each client
How do we connect a new client’s systems and odd log sources?
ARRTECH SIEM supports agent-based and agentless collection, depending on the source. If ARRTECH does not read a log source yet, we add a parser at no charge during the contract.
Who at the MSSP can see our data?
Only users granted access. Role-based rights limit each user to specific log sources and features, and ARRTECH DLP is multi-tenant too.
What will the next client cost us to run?
The cost depends on the client’s volume and service scope; shared administration reduces duplicated work. ARRTECH SIEM needs no separate operating system or database license.
What will we receive each month?
Each tenant’s reports arrive by email on a schedule, as PDF, DOC or XLSX.
What leaves with us when the contract ends?
The record. ARRTECH SIEM exports any source with its signatures and a standalone verifier, so the client’s auditor can check it without ARRTECH.
Who approved what was done for us?
The team. ARRTECH SOAR pauses a playbook at each step the team marks for approval and emails the approver the options. The history shows who chose what, and when.
