Business impact
See why the issue matters to the organisation and the type of consequence it may contribute to, using cautious outcome-oriented language.
WHAT IT CHECKS
What AssayMark checks — and what happens after it finds something
AssayMark reviews evidence smaller organisations often already have, then turns supported findings into context, priority, remediation and verification instead of stopping at a score.
SIGN-INS AND SERVER LOGS
See what’s happening
Supported logs can show repeated failed logins, access at unusual hours, unexpected changes and other events worth investigating. AssayMark turns those records into findings instead of asking you to read thousands of lines yourself.
Failed loginsUnusual accessUnexpected changesRecurring patterns
WEBSITE EXPOSURE
Check what’s visible from the outside
AssayMark reviews selected website security controls and exposure indicators, with authorised deeper assessment where appropriate. The aim is to show what is visible that should be tightened, not to run destructive tests.
Security headersExposure indicatorsAuthorised deeper checksPlain-English findings
SERVER AND APPLICATION SETTINGS
Check configuration without uploading the secrets inside it
For supported configuration files, your browser extracts an allow-list of non-secret settings. Passwords, database credentials, API keys, tokens and salts are never included and never leave your machine.
The non-secret settings received by AssayMark are independently re-validated on the server before a result is accepted.
FROM FINDING TO ACTION
A finding should answer more than “what is wrong?”
Where the underlying assessment supports it, AssayMark adds the information a business owner and the person implementing the fix need to move the issue forward.
Why this priority?
See the real scoring or prioritisation components that are available for that assessment. AssayMark does not invent factors that the underlying engine did not use.
Owner and timeframe
Actionable findings can identify a suitable responsible role and target timeframe so the work has a clear next owner rather than remaining an unassigned alert.
Fix and verify
Technical users can open remediation and verification guidance. Where AssayMark can safely re-check the issue it supports a re-test; otherwise manual verification is made explicit.
TWO CONTEXTUAL VIEWS
Business View for decisions. Technical View for implementation.
Business View focuses on impact, priority, owner, timeframe and the next action. Technical View exposes the supporting evidence, affected asset, available framework context, remediation steps and verification instructions.
What is wrong?
Why does it matter?
Why this priority?
Who should fix it, and when?
How is the fix verified?
Context → Priority → Action → Remediation → Verification
THE OUTPUT
Understand the risk. Know what to fix. Track what happens next.
AssayMark is designed to move supported findings through prioritisation, ownership, remediation and verification rather than leaving the user with an unordered list of alerts.