// ACCOUNT SEPARATION
Run the portfolio without blending the clients.
Each account is a complete operating boundary with its own environments, applications, domains, targets, schedules, scanner connections, members, scan history, and findings.
MSP administrators can move from the portfolio view into one chosen account. Customer users see only the account they belong to.
One account record from license to remediation
Commercial operations and security operations stay in the same scope, so a scanner, its runs, and the vulnerabilities it reports never lose their customer context.
LICENSES
Assign from a shared pool
See the MSP license pool, assign scanner connections to explicit accounts, and recover capacity when a connection ends.
SCANS
Local and cloud together
Cloud runs and completed scans pushed by customer or MSP scanners land in the same account-scoped timeline.
VULNERABILITIES
A history per target
Current findings, prior evidence, and recent runs remain attached to the target and account that produced them.
// CLOUD SCANS
Give every account an outside-in testing cadence.
Run NewScan Cloud against authorized web applications and APIs that are reachable from the public internet. Launch on demand or schedule explicit targets daily, weekly, or monthly.
The customer’s domain proof is rechecked before every launch. The target, authorization, schedule, run, and returned evidence all stay inside that customer’s account.
- 1Prove the domainPublish the account-specific DNS ownership record.
- 2Choose reachable targetsSelect only the web and API targets the cloud can access.
- 3Set the cadenceEvery launch repeats the authorization checks.
// ACCESS CONTROL
Four levels, scoped where work happens.
Assign each person the least access they need at the division or account boundary. Broader access stays explicit instead of leaking across the organization.
ADMIN
Set policy and access
Manage settings, structure, members, and permissions inside the assigned scope.
SCAN
Configure and run
Create targets and schedules, launch scans, and use triage and read capabilities.
TRIAGE
Review vulnerabilities
Investigate findings, maintain the working queue, and preserve the evidence behind each decision.
READ
See results
View scan results, vulnerability history, and the current security posture without changing them.
// BUILT FOR MSP WORK
The portfolio view and the customer view are different on purpose.
Portfolio control
Search accounts, compare last-scan activity and open findings, and see license capacity without entering each customer workspace.
Account operations
Choose one account before changing targets, schedules, scanner connections, members, or customer details.
Customer access
Invite customer users into their own account-scoped view without exposing another client’s inventory, scans, or evidence.
History retention
Suspend an inactive account while preserving the scan and vulnerability history your service delivered.
Scale the service, not the cross-account risk.
Give your team one place to operate while each customer keeps a separate security record, schedule, license scope, and access boundary.