EVYCOMPANY

EVY / Cybersecurity

Know your risks.
Fix what matters.

Offline static build checks, approved file corrections and version-bound retesting for websites you own or manage.

Authorized assets. Written scope. Evidence you can inspect.

Clarity before complexity.

01 / Establish the boundaries

A useful assessment starts with the right questions, the right permissions and a defined website.

We agree what to review, the access needed and the evidence you will receive. The scope determines the checks, depth, schedule and proposal.

Tell us what you need →
Build configuration
Supplied _headers files, literal resource URLs and agreed exposure checks.
Files supplied by you
Published files, source maps and credential-shaped strings in a bounded static bundle.
Ten bounded check classes
No live scanning, dependency audit, authentication testing or server-side review.
Evidence, always scoped
What was observed, the version reviewed, what matters and what remains unverified.

Choose the work that moves you forward.

02 / Three distinct engagements

01

EVY Security Baseline

Understand the starting point.

A limited offline review of one owner-supplied static website build. Ten configuration and exposure check classes, supporting evidence and practical priorities.

  • Written asset and check inventory
  • Observed risks and review limitations
  • Prioritized remediation plan
Request a Baseline
02

EVY Security Hardening

Turn findings into verified changes.

Approved fixes for identified issues. We agree the implementation, review the change and retest the current version before reporting delivery.

  • Agreed corrections and rollback plan
  • Focused tests and version-bound retesting
  • Delivery report and remaining risks
Discuss a fix
03

EVY Security Continuity Planned service

Keep the next change in view.

Periodic checks and regression follow-up are planned as a separately scoped engagement. Coverage and frequency must be agreed before service begins.

This is not an available 24/7 monitoring or incident response service.

Discuss future needs →

Every engagement starts with a written scope and a reviewed proposal. No automatic scans, fixed security tariff or online payment is offered here.

Permission. Evidence. A controlled next step.

03 / How the work progresses

You stay in control of the assets, the access and the changes.

A request is an enquiry. It does not authorize testing, accept a proposal or start a paid engagement.

  1. 01

    Request & scope

    Identify the website, the problem and the kind of help you need.

  2. 02

    Verify authorization

    Ownership or written permission, included assets, permitted methods and boundaries are checked before active analysis.

  3. 03

    Agree the proposal

    Deliverables, access, schedule and cost are confirmed in writing. Acceptance and authorized payment are separate steps.

  4. 04

    Assess & prioritize

    Run only the agreed checks. Record reproducible evidence and distinguish findings from unverified assumptions.

  5. 05

    Approve & remediate

    Implement the agreed fixes under the permissions you grant, with focused checks and a rollback route.

  6. 06

    Retest & report

    Validate the current asset version. Deliver the results, corrections and the limits of the review.

The report must match the website.

04 / Inspect our approach

Old evidence cannot approve a new version.

Our assessment workflow binds every report to the exact version it reviewed. When the asset changes, a report tied to the old version is refused until the new version has been retested.

The end-to-end demo takes a synthetic shop from request to report: written authorization, a static review of the supplied files, approved fixes, a retest and a report bound to the fixed version.

Both linked records were generated by running our code on synthetic files. They are not a customer assessment, a security certification or proof that any website has no vulnerabilities.

Open the workflow evidence record →

Open the end-to-end demo record →

LAB / EVIDENCE INTEGRITY
  1. 01 Asset A → validation A
  2. 02 Asset changes to B
  3. 03 Stale report rejected
  4. 04 Validation B → current report B

The record lists each step, its hashes and the refusal.

Start with the right scope.

05 / Request a Security Assessment

Tell us about your website and the decision you need to make.

Include only information needed to discuss the scope. Please do not send passwords, access tokens, exploit details or sensitive customer data.

You decide what happens next.

Your request is reviewed before a proposal. An entered URL does not trigger a scan or verify permission to test.

Prepare a brief in your browser, then download it or open it in your email app. Nothing is submitted automatically. Prefer email? Write to carlos@evycompany.com.

Clear boundaries. Straight answers.

Is this a full penetration test?

No. This service checks ten static configuration and exposure classes in files you supply. It is not a penetration test, a live scan or a security certification. Unsupported markup and unreviewed regions are disclosed in the report.

Will entering my website start a security scan?

No. We review the request, verify asset authorization and agree the assessment boundaries before any active analysis.

Can you guarantee that my website is secure?

No assessment can guarantee the absence of vulnerabilities. The report identifies the checks performed, evidence collected, version assessed and remaining limitations.

How are price and payment handled?

There is no fixed security price or checkout on this page. A reviewed proposal sets the scope and cost; payment becomes available only when the required approvals are in place.

Do you provide continuous incident response?

No. Security Continuity is a planned periodic service, subject to a separate agreement. It is not an available 24/7 security operations or incident response service.