Please read this! Title for this issue is a **`MANDATORY`** to follow this format [incident] Title of incident on j M Y H:i eg: [incident]Bad Gateway Error on 08 Feb 2020 16:00 Please remove this notice. ------ # Incident Response Report Template ## Information Required |Item || |----------------------------------------------------|---------------------------------------| |**Reference Number** | *(git2u group/project with issue ID)* | |**Company Name** | **Razer Merchant Services** | |**Incident Place** | *Mandatory* | |**Name and title of
person making the
report**| *Mandatory* | |**Applicable Law and Regulations** | *To be filled in for breaches of laws and regulations.
For breaches of laws and regulations, texts of governing laws and regulations should be attached. Please consult Legal & Regulatory Compliance.
`Whether or not the case should be reported to local authorities.`* | |**Date reported to the
Senior Management/
Risk & Compliance**| *Mandatory* | |**Period of Incident** | *Mandatory* | |**Incident Amount** | *To be filled in if applicable* | |**How did you find out
about the incident?
(With date)** | *Mandatory* | |**Outline of Incident** | *Mandatory*

Please describe events in a chronological order with dates and add
an explanation to abbreviations of organizations names and others.
The following information must be reported:
- findings and recommendations;
- root cause analysis;
- if some controls were in place to prevent related events
before the occurrence or discovery even if they are
insufficient;
- remediation and improvement plans. |**Status of the
investigation on
Incident** | *Mandatory*

The following points must be mentioned:
- whether or not relevant risks were pointed out in the past (e.g: by internal audit);
- risk and possibility of similar or repeated incident. |**Actions taken after
Incident** | *Mandatory*

1) Fraud : *Status of police report (if any) must be reported*

2) Cases involving customers : *Action taken must be reported.*

3) Company losses and fines due to failure and negligence of third party
Whether or not the Company sought for indemnification or recovery
and the status. |**Root Cause Analysis** | *Mandaroty*

Please go to root causes | |**Measures of
Recurrence
Prevention/
Lessons Learned** | *Mandatory*

Please explain clearly the effectiveness of prevent
recurrence and limitations if any |**Personnel Penalty

For persons causing
the Incident** | To be filled in for frauds, breaches of laws and regulations, cases
causing company losses, information leakage and incidents which
have the potential of causing significant damage to the Company's
reputation and credibility.
(including when the Senior Management decides not to impose a
penalty) |**Comments by
Regulatory
Compliance and/or
Risk Management** | *Mandatory*

Regulatory Compliance and/or Risk Management are to:
1) Assess if the case is an isolated error or suggests lack of controls
and to comment or make recommendations;
2) Assess the possibility of similar incidents and comment or make
recommendations; and
3) evaluate the reasonableness, sufficiency and effectiveness of
investigation, actions taken after incidents, cause analysis and
measures of prevention and personnel penalty and to comment or
make recommendations. |**Reports to the
Senior Management
and the Chief Legal
& Compliance
Officer of Razer Inc.
and their
instructions** | *Mandatory*

Reporting method and their instructions should be reported ## Infra Team Checklist *Network* - [ ] SSL Cert - [ ] Domain Name (Akamain, CloudFlare) - [ ] Load Balancer *Server* - [ ] Server status *(CPU, Memory, Storage, Network)* - [ ] Glogger - [ ] System - [ ] Service *Database* - [ ] Database Status *(Replication Delay, CPU, Memory, database connection)* ## Programmer Team Checklist - [ ] New Relic APM *(Response Time, Throughput, PHP, Database, Web External)* - [ ] Queue Worker in Gearman Worker on Payment Server - [ ] Latest Deployment - [ ] Source Code or Application Log ## Ops Team Checklist - [ ] Channel affected details *(How many channels affected, Online or Offline)* - [ ] Announcement for unexpected downtime for channel affected and inform VIP merchant /assign me /label ~"Type::Incident" ~"Type::Documentation"