Security at Data Mammoth — How We Protect Your Data

Security is fundamental to everything we do at Data Mammoth. From physical data center security to application-level protections, we employ multiple layers of defense to keep your data and infrastructure safe. This guide provides an overview of our security practices and the tools available to secure your own services.

Infrastructure Security

Data Center Security

Our data centers feature enterprise-grade physical security:

• Access control — Biometric authentication and keycard access for authorized personnel only.
• 24/7 surveillance — CCTV monitoring with recording and retention.
• Environmental controls — Fire suppression, climate control, and redundant power systems.
• Redundant connectivity — Multiple upstream network providers for high availability.

Network Security

• DDoS mitigation — Automated detection and filtering of volumetric attacks. See DDoS Protection.
• Network monitoring — Continuous monitoring for anomalous traffic patterns.
• Firewall protection — Network-level firewalls filter malicious traffic before it reaches your server.
• Traffic encryption — API and dashboard communications are encrypted with TLS 1.2+.

Hypervisor Isolation

Each virtual server runs in an isolated environment:

• Strict resource isolation between virtual machines.
• Regular hypervisor security updates.
• No cross-tenant data access.

Data Protection

Encryption

• In transit — All data between your browser/applications and Data Mammoth is encrypted via TLS.
• At rest — Storage encryption protects data on physical disks.
• API communication — HTTPS is enforced for all API endpoints.

Backup and Recovery

• Automated backups — Available as an add-on for regular server snapshots. See Backup Strategy.
• Snapshot technology — Point-in-time recovery capabilities.
• Geographic redundancy — Backup storage in separate locations for disaster recovery.

Account Security

Data Mammoth provides several features to secure your account:

Two-Factor Authentication (2FA)

Enable 2FA to require a verification code in addition to your password. See Enable 2FA — Protect Your Account.

SSH Key Authentication

Use cryptographic key pairs for server access instead of passwords. See SSH Key Best Practices.

Activity Logging

All account and server actions are logged for audit purposes. See Viewing Server Activity Log.

Password Policies

Strong password requirements protect against brute-force attacks.

Your Security Responsibilities

While Data Mammoth secures the infrastructure, you share responsibility for securing your services:

Server-Level Security

• Keep software updated — Apply OS and application updates regularly.
• Configure firewalls — Restrict access to only necessary ports. See Server Firewall Hardening Guide.
• Use SSH keys — Disable password authentication for SSH. See SSH Key Best Practices.
• Install fail2ban — Protect against brute-force login attempts.
• Minimize attack surface — Disable unnecessary services.

Application-Level Security

• Use SSL/TLS — Encrypt all web traffic with HTTPS. See SSL/TLS Certificates.
• Keep applications updated — WordPress, PHP, databases, and other software.
• Use strong credentials — Unique, strong passwords for all services.
• Input validation — Protect applications against injection attacks.
• Regular security audits — Review your security posture periodically.

Account Security

• Enable 2FA — Protect your Data Mammoth account.
• Use unique passwords — Never reuse passwords across services.
• Review access — Regularly audit who has access to your account and servers.
• Monitor activity — Check activity logs for unauthorized actions.

Security Compliance

Data Mammoth maintains security practices aligned with industry standards:

• Regular security assessments and penetration testing.
• Incident response procedures for rapid threat containment.
• Employee security training and access controls.
• Data handling practices compliant with applicable regulations.

Incident Response

If we detect a security issue affecting your services:

Immediate containment — We take steps to contain the threat.

Notification — You are notified promptly with details about the incident.

Investigation — Our security team investigates the root cause.

Remediation — We implement fixes and preventive measures.

Report — A post-incident report is provided when applicable.

Reporting Security Issues

If you discover a security vulnerability:

Submit a support ticket marked as Critical priority.

Describe the vulnerability in detail.

Do not disclose the vulnerability publicly until it has been addressed.

Security Resources

Explore our security guides for detailed hardening instructions:

• Enable 2FA — Protect Your Account
• SSH Key Best Practices
• Server Firewall Hardening Guide
• SSL/TLS Certificates — Setup & Renewal
• DDoS Protection — What We Offer
• Backup Strategy — Snapshots, Offsite, Automated
• Complete Server Security Checklist

What to Do Next

• Enable 2FA — Protect Your Account — Secure your account first.
• Complete Server Security Checklist — Full hardening guide.
• Server Firewall Hardening Guide — Lock down your server.
• Backup Strategy — Protect against data loss.