EKKLESIA.NG SECURITY INCIDENT RESPONSE POLICY

1. What Is a Security Incident?

A security incident may include:

• Unauthorized access.
• Suspected account compromise.
• Unauthorized disclosure.
• Malware.
• Data breach.
• Credential compromise.
• System intrusion.
• Loss of protected information.
• Significant security vulnerability.

Not every security event constitutes a personal-data breach.

2. Detection

Security incidents may be identified through:

• Automated monitoring.
• Security alerts.
• System logs.
• Staff reports.
• Customer reports.
• Third-party notifications.
• Vulnerability reports.

3. Initial Assessment

When an incident is identified, Ekklesia may assess:

• What happened.
• Which systems were affected.
• Whether customer information was involved.
• Whether personal data was affected.
• The scope of the incident.
• The likely impact.
• Whether containment is required.

4. Containment

Depending on the incident, Ekklesia may:

• Disable affected accounts.
• Revoke credentials.
• Rotate credentials or keys.
• Isolate systems.
• Block malicious traffic.
• Disable affected integrations.
• Apply security patches.
• Restrict affected functionality.

5. Investigation

Ekklesia may investigate:

• System logs.
• Authentication records.
• Access records.
• Application activity.
• Infrastructure activity.
• Relevant third-party systems.

Where appropriate, specialist security providers may assist with the investigation.

6. Customer Notification

Where Ekklesia determines that a security incident materially affects customer data, we will provide notice as required by applicable law and contractual obligations.

Notification may include:

• General description of the incident.
• Categories of affected information.
• Known or suspected impact.
• Measures taken to contain the incident.
• Recommended customer actions.
• Contact information for further questions.

We may delay notification where legally permitted or required to avoid compromising an investigation.

7. Customer Responsibilities

Customers should promptly notify Ekklesia if they suspect:

• Unauthorized account access.
• Compromised credentials.
• Suspicious activity.
• Unauthorized data disclosure.
• Abuse of messaging services.

Reports should be sent to: security@ekklesia.ng

For urgent security matters, customers should include URGENT SECURITY INCIDENT in the subject.

8. Evidence Preservation

Where appropriate, Ekklesia may preserve relevant logs and evidence for investigation, legal proceedings, security analysis or regulatory requirements.

9. Remediation

After containment, Ekklesia may:

• Patch vulnerabilities.
• Improve security controls.
• Reset credentials.
• Review access permissions.
• Update monitoring.
• Improve infrastructure.
• Conduct post-incident analysis.

10. Third-Party Incidents

Where an incident originates from a third-party service provider, Ekklesia will coordinate with that provider where appropriate.

Ekklesia cannot guarantee the actions, availability or security of independent third-party services.

11. No Absolute Security Guarantee

Ekklesia implements reasonable technical and organizational safeguards but cannot guarantee that its services will never experience:

• Cyberattacks.
• Security vulnerabilities.
• Unauthorized access.
• Service disruption.
• Data loss.

Customers are responsible for maintaining appropriate account security and access controls.

12. Responsible Disclosure

Security researchers who discover a potential vulnerability should contact: security@ekklesia.ng

Researchers should avoid:

• Accessing customer data.
• Disrupting services.
• Destroying data.
• Publicly disclosing vulnerabilities before reasonable remediation time.