APPSEC
CZ SK EN
FROM THE FIRST QUESTION TO VERIFICATION

How we work

Every engagement is different, but the process remains predictable. You know in advance what we will need, what you will receive and who is responsible for each step.

AN AGREED SCOPE EXAMPLE

Know what you will receive before work starts.

What you need to learn Goal: assess access to orders Scope: portal web application and API Deliverable: evidence, impact, remediation
  1. What you need to learn
  2. What we will assess
  3. What we will deliver
Goal → scope → deliverable → next steps.

We agree on the rules and deliverable before work begins. Remediation, retesting and support have an agreed scope.

First contact
A few sentences about your situation and objective. No lengthy questionnaire.
Before delivery
Confirmed scope, rules, responsibilities and deliverables.
After delivery
An explanation of the results; retesting or support where included in the proposal.
  1. 01
    UNDERSTANDING

    Let's discuss your situation

    We want to understand your situation, environment and the decision you face. A short description is enough. Do not send credentials, code or sensitive documents at this stage.

  2. 02
    PROPOSAL

    Define scope and responsibilities

    We agree objectives, deliverables and the boundaries of the work. For testing, this means authorisation and Rules of Engagement; for technology, licences, deployment and support.

  3. 03
    PREPARATION

    Set up safe working conditions

    We agree a secure way to share information. We confirm contacts, authorised targets and the test environment, or a pilot group of devices.

  4. 04
    DELIVERY

    Perform the test, analysis or deployment

    We work within the agreed boundaries and keep you informed about important developments. A critical finding is reported according to the escalation agreement; it does not wait for the final report.

  5. 05
    HANDOVER

    Explain the deliverables and next steps

    Management receives a risk summary and priorities; the technical team gets reproduction steps and recommended fixes or configuration guidance. For technologies, we clearly distinguish the product, our support and any managed service.

  6. 06
    VERIFICATION

    Verify the outcome as agreed

    A retest after remediation verifies whether the original findings have been resolved. For technology, the next step may be an extended pilot or support within the agreed scope.

RESPONSIBILITIES

Three roles, clear boundaries.

Customer

Describes the environment, provides authorisation and technical cooperation, and approves operational changes.

APPSEC

Performs the agreed professional work: testing, analysis, design, deployment or support within the proposal's scope.

Technology vendor

Supplies the product and defines the licensing terms. Any SOC or MXDR service it offers is not an APPSEC service.

INITIAL CONVERSATION, NO OBLIGATION

Not sure where to start? Tell us what you are facing.

You do not need to know whether you need a test, a technology or a consultation. We will suggest a suitable next step based on your situation.

Arrange a consultation