Partners · testing firms and MSSPs
Know what changed at every client since your report.
Your report describes the application on the day you tested it. Vikax records what you covered, monitors each client's production from the outside and shows you what changed before the client asks.
For a testing firm
What changes after you deliver the report.
Record what the assessment covered, watch the client's production from the outside and scope the next test from what changed.
Record what you tested
When you deliver the report, Vikax seals a record of the pages and APIs the assessment covered. Every later comparison starts from that record.
Know when a client's application changes
Vikax checks the client's application from the outside and shows how far it has moved since your test.
Scope the next test from evidence
Vikax names the areas each change touches, with OWASP references. Scope the follow-up test to what changed, with the evidence attached.
Keep the record
Nobody can edit a decision or an outcome. Exports in PDF, HTML, JSON and ZIP go into the client file with their audit entries.
Every client in one console
Vikax groups applications by client and shows the days since each assessment, the open changes and the open testing decisions.
Alerts where your analysts work
Vikax sends alerts to Slack, Microsoft Teams, Discord, signed webhooks or email, for each change or as a digest in your time zone.
The console
Every client in one console.
This is what your team sees: each client's applications, what changed since your report, and the testing decisions still open.
The engagement, after the report
From the report to the next test.
One line per engagement: the record sealed on delivery, routine checks, the change that matters, your analyst's decision and the testing that follows.
The report is delivered
Vikax seals a record of what the assessment covered: the pages and APIs in scope, and the two left out, each with a reason.
A release nobody planned
Four changes reach the client's customer portal overnight, including a new third-party script on the checkout page.
Your analysts hear first
The change reaches your team in Slack and in the morning digest, with a link to the page before and after, before the client asks.
A security policy is widened
The content security policy on the account page now allows a new script source. The page was in scope for your test.
Your analyst decides
A. Hassan records targeted testing of the account page, with a reason. Nobody can edit the decision afterwards.
The next test, scoped by the evidence
The test covers what changed. The outcome is recorded, and the client receives the evidence as a PDF and a ZIP.
For a managed security service provider
Your clients control access, and your team runs the work.
Clients you manage sit side by side in your workspace. Clients with their own workspace approve your access, each grant names an analyst and covers specific applications, and every use is recorded.
Access the client approves
A client lets your analysts in through a connection it approves. Until it does, your team sees nothing.
Grants for named analysts
Each grant names one analyst and covers specific applications, environments or assessments, with seven kinds of permission.
Roles that fit a provider
Five roles (owner, admin, analyst, viewer and billing admin) keep configuration, review and billing with different people.
Digests on your schedule
Choose immediate alerts for some destinations and a digest on your days and time for others.
Every access recorded
Each access through a grant is written to an audit log that cannot be edited and is kept for at least 400 days.
Plans sized for many clients
Professional covers 150 monitored pages, APIs or files and 10,000 checks a day. Enterprise covers 1,000 and 100,000. Both include the API.
Questions
Common questions
Book a demo
Show your clients what changed since your last report.
A walkthrough of recording a delivery, release review and a testing decision on sample data, with the team that built Vikax.