Governance

Governance & Incident Response

Clear roles from the Compliance Committee down to every staff member, and a deadline for every step after an incident. Report first, investigate later.

Incident clockSOP-PDP-001
1 h Discover & reportT+0
4 h EscalateCommittee
3×24 h Notify authorities & data subjectsUU PDP
14 d CloseRoot cause

// 01 STRUCTURE

Six levels, clear responsibility

Clear roles and responsibilities from the Compliance Committee down to every staff member.

24/7

The ISMS Manager, IMO and team leaders are on call 24/7, 365 days a year.

  1. 01

    Compliance Committee

    Top body: approves compliance, sanctions and external notices

  2. 02

    ISMS Manager

    Owns the ISMS; reports on risks and controls

  3. 03

    IMO (Information Management Officer)

    Leads company-wide reviews; reports to the Committee

  4. 04

    Team Leader

    Checks each project team's compliance daily

  5. 05

    Assistant Team Leader

    Supports the leader with daily monitoring

  6. 06

    Staff

    Apply security measures in daily client work

// 02 REVIEW

Company-wide review every 6 months

Every staff member's compliance is assessed twice a year and kept as an auditable record.

H1January–June
H2July–December
  1. 01

    Assess

    The IMO and ISMS Manager assess every level with a standard form.

  2. 02

    Consolidate

    Findings, evidence and status are compiled and verified.

  3. 03

    Record

    The Committee records results and keeps them for audit.

  4. 04

    Follow up

    Any violation gets a corrective action with a deadline.

// 03 INCIDENT RESPONSE

Report first, investigate later

Every step has a deadline, from discovery to closure.

  1. Within 1 hr

    Discover & report

    The finder reports to their manager. Estimates are fine.

  2. Within 4 hrs

    Escalate

    Set the severity, start containment, escalate to the Committee.

  3. Promptly · 3×24 hrs

    Notify

    Inform the client and management promptly; authorities and data subjects within 3×24 hours.

  4. Within 14 days

    Close

    Restore service, record the root cause and fixes, then close.

SeverityWhat it means
High Data leaked outside, large volume, or active misuse
Medium Limited general personal data may have leaked
Low Internal issue with no external leak

A no-blame culture means even small issues are shared early. When in doubt, we choose the higher severity.

// PEOPLE

People measures

In the end, security depends on people. Everyone works by the same rules.

01

SOPs mandatory for all

Programmers, QA, PMs and management all know and follow incident procedures.
02

Semi-annual assessment

All staff complete an assessment form twice a year, approved by the IMO and Committee.
03

24/7 emergency contacts

The ISMS Manager, IMO and team leaders are on call 24/7, 365 days a year.
04

High retention

Only 2 people left in 4 years, so knowledge stays in-house and controls never lapse.

// 04 ENFORCEMENT

Records & enforcement

Assessments are recorded in writing, with clear sanctions by severity.

Assessment form
  • Date, employee name, position
  • Department and client project
  • Security items assessed
  • Status: compliant / needs work / non-compliant
  • Findings and supporting evidence
  • Corrective action and deadline
  • Assessor (IMO) and Committee approval

Minor

One-off, low-impact lapse. Verbal warning from the Team Leader or ISMS Manager, recorded.

Minor

Medium

Repeated or uncorrected lapse. Formal written warning after Committee review.

Medium

Severe

Client-impacting or intentional violation. Decided by the Committee; may mean final warning or dismissal.

Severe

LET'S TALK

Try us on a small project first.

During the trial you can check our communication and quality before signing a full contract.

  1. 01 Inquiry
  2. 02 Discovery
  3. 03 Proposal & quote
  4. 04 Trial
  5. 05 Contract & build