Book a demo

Security teams

Know which applications changed since their last test.

Vikax monitors your production web applications from the outside and shows how far each one has moved since its last test. Your team sees which releases were planned and decides what needs testing.

Book a demoSee the platform

The console

Every application on one screen.

This is what your team sees: each application, how far it has moved since its last assessment, whether its latest release was confirmed, and the testing decisions still open.

For a security leader

What you can show the board and the auditor.

  • How far each application has moved

    Six states, from stable to a major change in the tested areas, next to the days since the last assessment. A state describes change and is never a security score.

  • Releases your teams can account for

    Vikax groups changes into releases. Delivery teams confirm the ones they planned under their own change reference, and the rest go to review.

  • A recorded decision on testing

    An analyst records one of five decisions and, later, the outcome. Nobody can edit a decision, so the history shows who decided what and why.

  • Evidence for the auditor

    Export an application, a release or a period as PDF, HTML, JSON or ZIP. Audit logs cannot be edited and are kept for at least 400 days.

  • Your data stays in your workspace

    Each workspace is isolated from every other. Stored credentials and alert destinations are encrypted, and platform admins cannot see customer content.

  • Read-only in production

    Vikax only reads, from the outside, on ports 80 and 443. It cannot reach private networks, and each response stops at 25 MiB or 30 seconds.

The gap between tests

A penetration test describes one day. Releases keep coming.

Between assessments the application keeps changing: headers, scripts, routes and third parties. Vikax keeps a record of every change and of what your team decided.

14 Mar · Test day

The assessment ends

The report describes the customer portal as it stood that day. Vikax seals a record of what the test covered.

Assessment record sealed
Week 3

A planned release

A checkout redesign ships with a new script. Your analyst confirms it under the change reference CR-10482.

ConfirmedCR-10482
Week 9

A change nobody claimed

Overnight, the security policy is widened and a header the test relied on is removed. Nobody confirms the release.

Not confirmedSignificant change
Week 9 · Decision

A decision on testing

Your analyst reads the evidence and records targeted testing of the login and account pages, with a reason.

Targeted testingAuthentication
Month 7

Six months on

When the board asks whether the March test still holds, you answer with every change, release and decision since.

Every change recordedAudit log

Questions

Common questions

No. Vikax shows whether an application still matches what was tested and what your team decided about each change. It never gives a security score. Our post on assessment freshness explains what each state describes.

Nothing. Vikax checks the pages and APIs you choose from the outside, the way any visitor can reach them.

Your delivery team confirms each release it planned and records its change reference. Releases nobody confirms stay open for review. Vikax does not connect to ticketing tools today.

Only people in your workspace. Platform admins cannot see customer content. A testing provider gets access only through a connection you approve, limited to named analysts and recorded in the audit log.

Book a demo

See how the record answers an auditor's questions.

A walkthrough of applications, releases and testing decisions on sample data, with the team that built Vikax.

Book a demoTalk to the team