Customers can check for themselves
Incidents, coverage, exposure and reports are available to them without raising a request.
- SOC 2 Readiness
- 24/7 Security Monitoring
- Canadian-Based SOC
GuardsArm Platform · Platform
Client Portal
Give each customer their own view of the service, without giving them the analyst console.
A managed service is judged on what the customer can see. The Client Portal is the customer-facing side of the platform: their incidents, their coverage, their exposure and their reports, and nothing that belongs to anyone else.
- Customer-facing
- Tenant-isolated
- Reports and SLA
Client Portal
Monitoring- IncidentsLive
- Assets and coverageVisibility
- Vulnerability exposureRisk
- Reports and SLAService
Each customer sees their own data and nothing else.
What is at stake
A service the customer cannot see is a service they question at renewal.
Fewer status requests to your analysts
Questions the portal answers do not need a person to answer them.
The agreement is visible
Service and SLA information sits beside the work being done.
Who carries this
Carried by the service delivery lead at the provider, and used by the customer contact who reports upward on the service.
The problem
Customers want to see the service, not operate it
A customer of a managed security service has a small number of questions. Is anything happening to us right now? Are all of our machines covered? What are we exposed to? Are you meeting the agreement? Can I have the report for my board?
The analyst console can answer all of them, and is the wrong thing to hand over. It is built for people who work alerts all day, and it shows a provider view across many customers.
The Client Portal answers those questions in a view made for the customer, scoped to their tenant.
What a customer cannot see, they tend to assume is not being done.
Capabilities
What customers get
A dashboard for the customer
A summary view written for the person receiving the service, separate from the operator command center.
Incidents, assets and coverage
Customers can follow their own incidents and see which of their assets are covered.
Threat map and vulnerability exposure
The customer view of where activity is coming from and what is exposed in their environment.
Compliance
Their compliance position, drawn from the same posture data the operator sees.
Service, SLA and support
Service and SLA information, and support and contact details, in the portal itself.
My Reports
The reports produced for that customer, available to them directly.
How it fits the platform
The portal is a view onto a tenant, and tenant isolation is enforced in the data layer. A customer sees only their own data because the platform will not return anything else, not because a screen hides it.
How it works
How a customer comes to have a portal
The portal follows from how tenants work on the platform.
The customer is onboarded as a tenant
Each customer is a tenant, and their agents map to their own group.
Isolation is applied in the data layer
The tenant can only be served its own data. This is enforced where the data is stored and through role-based access, not only in the interface.
The customer signs in to their view
They see the portal sections for their tenant and nothing from the operator console.
Reports arrive where they can find them
Reports generated for the customer are available under My Reports.
It can carry your brand
For providers delivering the platform as their own service, the interface can be re-branded.
Questions
Common questions
Can a customer see another customer’s data?
No. Each customer is a tenant and isolation is enforced in the data layer and through role-based access, so a tenant is only ever served its own data.
What does a customer see in the portal?
A dashboard, their incidents, assets and coverage, a threat map, vulnerability exposure, compliance, service and SLA information, support contacts and their reports.
Can the portal carry our own brand?
Yes. The platform interface can be re-branded for providers delivering it as their own service.
Works with
The modules next to this one
Every module runs in the same self-hosted stack and shares the same telemetry, severity model and response engine.
See Client Portal running on your own infrastructure
We will walk through the console, the deployment model and what it takes to stand it up in your environment.
24/7 SOC Monitoring Available