Information Security & Operations Policy

1. Overview

This policy defines the security and operational framework for our internal automation systems. We are committed to maintaining the highest standards of data integrity and network security for our e-commerce operations.

2. Infrastructure & Network Isolation

We maintain a robust network defense architecture designed to protect internal assets from external threats:

Network Segmentation: Our operational infrastructure is physically and logically segmented. Production workloads (n8n/Store APIs) are deployed on dedicated cloud instances entirely isolated from local office networks. Access is restricted to authorized personnel via SSH key-only authentication.
Intrusion Detection & Prevention (IDS/IPS): We implement multi-layered protection on all server nodes:
- HIPS (Host-based Protection): Using Fail2Ban to automatically detect and ban suspicious IP patterns and brute-force attempts in real-time.
- Firewall Hardening: Utilizing UFW/iptables to enforce strict ingress/egress filtering, closing all non-essential ports.

3. Automated Security & Monitoring

We implement “Security-as-Code” to ensure the reliability of our automated workflows:

# Example: Internal Security Enforcement Logic (N8N Workflow)
IF (execution_failed) {
    TRIGGER: Error_Workflow_Alert;
    ACTION: Push_Alert_to_DingTalk_Feishu;
    PAYLOAD: Extract_Error_Context; // Exclude PII
    LOGGING: Write_to_Internal_Audit_Log;
}

Every automated task is logged within our private NocoDB environment to ensure full auditability and traceability of data operations.

4. Data Protection & Privacy

Encryption: All data in transit is protected via TLS 1.2+ encryption.
No Third-Party Exposure: Internal data never leaves our controlled infrastructure. We do not engage in external data enrichment that requires exposing sensitive operational information.
Access Control: We adhere to the Principle of Least Privilege; access to production environments is granted only to specific automated service accounts.

5. Incident Response

In the event of a security incident, our team follows a strict protocol:

Immediate revocation of affected API credentials.
Isolation of the compromised server node/container.
Root cause analysis and formal reporting to relevant stakeholders.