Assessment coverage
The report lists the systems, applications and finding sources checked. It also identifies areas that could not be assessed.
We assess your systems, applications and code. We verify findings and prioritise fixes. After changes, we test whether the issues are resolved.
Compare care plansYou get verified findings and a remediation plan. We retest the reported issues after fixes.
The report lists the systems, applications and finding sources checked. It also identifies areas that could not be assessed.
You get verified findings and an assessment of their business impact. We separate issues needing action from duplicates and false alarms.
The plan prioritises fixes by risk and the system’s importance. It names an owner and deadline, and records the status of each fix.
After a fix, we retest the reported issue. We record the result and the version checked, including any issue that remains unresolved.
Every plan includes the full assessment cycle. We agree the scope, review frequency and support.
For regular checks, verified findings and a remediation plan for your systems and apps.
net per month1 hour of changes each monthUp to 10 assets and 1 application
For frequent changes that need weekly checks, closer follow-up and a faster response.
net per month3 hours of changes each monthUp to 25 assets and 3 applications
For multiple apps and teams needing tailored tests, integrations and support arrangements.
Project and care tailored to youAn agreed change allowanceScope matched to your environment
Before work begins, we agree the systems, applications, assessment methods and full price. We first use suitable tools and licences you already hold. Any additional solutions and setup are priced separately. Response means starting work on a verified critical finding, not completing the fix.
Finding validation, reports, remediation tracking and agreed retests are included in ongoing care outside the change allowance. The change allowance renews monthly and does not roll over. You are not charged twice for work already covered by another service.
This fictional example shows a finding and how we handle it. It is not a customer assessment result.
The library needs an update.
The report identifies the library, its version and affected deployments. We record evidence and the conditions that make the application vulnerable.
Risk determines the priority.
We assess whether an attacker can reach the vulnerability, its potential impact and existing safeguards. Priority reflects actual use, not just a severity score.
An owner and a deadline.
We agree an update or a temporary safeguard. The plan names an owner, sets a deadline and records how the work needed to fix the issue will be charged.
We check the fix.
We test the change in the specified version and all affected deployments. We record the test result and keep unresolved issues open in the issue register.
Assessment, finding analysis and retests form one service.We agree the methods and detailed scope before taking over.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Assets covered | Up to 10 | Up to 25 | As scoped |
| Applications covered | 1 | Up to 3 | As scoped |
| Full assessment cycle | Monthly | Weekly | As needed |
| Public service checks | Weekly | Daily | As scoped |
| New vulnerability advisories | Automated, daily | Automated, daily | As scoped |
| Code, dependencies and secrets | After method qualification | After method qualification | Dedicated scope |
| Validation and agreed retests | Included | Included | As agreed |
| Remediation progress review | Monthly | Weekly | As needed |
| Summary report | Monthly | Monthly | Agreed frequency |
| Planned changes | 1 hour per month | 3 hours per month | Agreed allowance |
| Critical finding response | Within 4 business hours | Within 60 min in office hours | Under the agreed SLA |
| Scope inventory | We record the assets, publicly accessible services and data sources covered by the assessment. |
|---|---|
| Assessment methods | We select external and authenticated checks where they are available and agreed. |
| Coverage gaps | We identify areas checked and omitted, including failed scans or unavailable access. |
| Scope qualification | The 10-asset and 25-asset limits are baseline profiles. Before starting, we confirm targets, systems, roles and the complexity of the environment. |
| Assets and applications | One server can host several applications. We confirm licence counting rules for the selected tool. |
| Assessment areas | We select tests of the running application, dependency analysis, exposed credential detection and code security checks. |
|---|---|
| Agreed coverage | We record the repositories, languages, roles, test accounts and scenarios included in the assessment. |
| Code analysis | This requires appropriate access and a tool that supports the code being checked. |
| Technologies | After checking tools and access, we can cover PHP, Python, JavaScript, TypeScript and .NET. |
| Checks after changes | We enable these after checking integration with the code change process. |
| In-depth assessment | Manual audits and application logic testing have a separately agreed scope. |
| Full assessment cycle | Agreed checks and a review of the results: monthly in Standard, weekly in Business. |
|---|---|
| Public service checks | We check selected externally visible changes: weekly in Standard, daily in Business. |
| New advisories | We match available advisories against the current asset inventory every day. This is not a daily manual audit of the entire application. |
| Validation and priority | We verify significant findings and consolidate duplicates. Priority considers exploitability, service importance, impact and safeguards; an automated alert still needs assessment. |
| Issue register | Each accepted issue has a recommendation, owner and deadline, or a recorded risk acceptance decision. We track remediation progress. |
|---|---|
| Retesting | After a fix is reported, we test the agreed version and record the result. A failed scan does not confirm that the vulnerability is fixed. |
| Change allowance | Standard: 1 hour per month; Business: 3 hours per month. A small fix may use the agreed allowance; unused time does not roll over. |
| Additional work | Larger code repairs are quoted separately. Additional administration: PLN 300 net per hour, after budget approval. |
| Our errors | We correct these without using your change allowance. |
| Covered events | A verified critical finding: we start assessment or an agreed protective action. This is the time to start handling the issue, not a repair deadline. |
|---|---|
| Response time | Standard: within 4 business hours; Business: within 60 minutes during office hours. |
| Clock start | From the earlier monitoring alert or receipt of a report through an agreed channel. Later confirmation that the finding is critical does not move the start time. |
| Office hours | Monday–Friday, 09:00–17:00 Warsaw time, excluding Polish public holidays. Outside these hours, the clock starts when the office opens. |
| Outside office hours | Business receives priority handling subject to availability, without a guaranteed human response time. |
| Repair deadline | This depends on risk, access and the supplier. We agree any temporary safeguard for the specific issue. |
| Tool selection | We use qualified customer tools, our own automation or suitable vendor solutions. We confirm coverage, usage rights, data access and export capabilities. |
|---|---|
| Additional costs | Required licences and resources are listed before work starts, without automatic charges. |
| Shared responsibility | When endpoint protection, access care or managed hosting also applies, we agree one division of responsibility. The same updates, licences and activities are charged once. |
| Existing care | An existing service may already be sufficient for a single website. |
| Report contents | Risk summary, coverage and gaps, verified findings, evidence, recommendations, owners and deadlines. Monthly reporting covers both Standard and Business. |
|---|---|
| Remediation status | The register shows progress, accepted exceptions and the retest result for the specified version. |
| Data history | Reports: 12 months; working material: 90 days. Agreed access and data minimisation rules apply. |
| Limits of the result | An assessment with no findings does not prove that the system has no vulnerabilities. |
| Before testing | We check scope, testing permissions and the existing process. Before active testing, we agree targets, accounts, the work window, limits and stop conditions. |
|---|---|
| New setup | Standard: from PLN 2499 net; Business: from PLN 4999 net. New setups have a one-month notice period. |
| No-fee takeover | A small takeover of a functioning process may qualify for no setup fee, with three months’ notice. New setup prices do not apply to every takeover. |
| Larger scope | Integrations and overdue repairs are quoted before work starts. |
| One-off project | You can commission a project without an ongoing subscription. |
| Data handover | We provide the scope inventory, findings register, reports, agreed procedures and available exports. |
| Ending operations | We agree alert handover, removal of granted access and data handover dates. |
| Licence obligations | Obligations to licence providers are documented separately. |
We review systems, applications and tools, then agree targets, access, testing conditions, responsibilities and price.
We set up agreed checks and verify their coverage. We validate findings and name an owner and deadline for each fix.
We track findings and fixes, make agreed changes and retest. We report current risks, assessment coverage and open decisions.
Care provides regular vulnerability assessment and remediation follow-up. A full manual penetration test covering roles and application logic is a separate project. We explain the methods and coverage before you choose.
We agree who will fix each issue: CyberON, your administrator, developer or supplier.
We agree a temporary safeguard or another way to reduce risk. We record the next steps and keep the unresolved issue in the register.
Yes, once we confirm testing permissions, access and support for the agreed tools. We also need contact with the person responsible for fixes.
Describe the systems and applications you want assessed. We will agree assessment methods, responsibilities and a quote.
Ask about scope and pricing