top of page

The FTC Settlement with GoDaddy Highlights the Imperative of Strong API Security

This guest post was contributed by Eric Schwake, Director of Cybersecurity Strategy at Salt Security

Eric Schwake, Director of Cybersecurity Strategy at Salt Security

In the digital age, APIs (Application Programming Interfaces) are the lifeblood of modern business operations, enabling seamless connectivity and data exchange across various platforms and services. However, this interconnectedness also introduces significant security and privacy risks. The recent settlement between the Federal Trade Commission (FTC) and GoDaddy underscores the critical importance of robust API security measures. This case serves as a stark reminder that ensuring API security is not merely a best practice but a legal obligation.


GoDaddy’s API Security Breaches


The FTC's actions against GoDaddy were prompted by the company's failure to implement adequate security measures, leading to multiple data breaches between 2019 and 2022. These breaches exposed sensitive customer information, including usernames, passwords, and employee credentials. The FTC’s investigation revealed several critical API security lapses:

  • Inadequate API Authentication: Lack of multi-factor authentication (MFA) and encryption compromised sensitive customer data.

  • Insufficient API Monitoring: Absence of rate-limiting, logging, and anomaly detection allowed unauthorized access to 1.2 million customer records.

  • Weak Access Controls: Disclosure of admin credentials and encryption keys enabled attackers to compromise websites.


FTC-Required API Security Measures


As part of the settlement, the FTC mandated a comprehensive security regimen for GoDaddy, including:

  • Encrypted API Communications: Mandatory use of HTTPS and TLS encryption for data in transit.

  • Access Control: Authentication methods to safeguard session authenticity and protect against session hijacking.

  • Rate Limiting: Implementation of rate limiting to prevent abuse and distributed denial-of-service attacks.

  • Monitoring & Anomaly Detection: Diligent monitoring of API traffic for suspicious activities.

  • Audit Logs & Incident Response: Maintenance and analysis of API security logs to detect and respond to breaches.


Implications for Law and Business


The GoDaddy settlement underscores the significant legal and business consequences of inadequate API security. Companies that fail to secure their APIs may face:

  • Regulatory Risks: Increased scrutiny and potential financial penalties from the FTC.

  • Reputation Damage: Loss of customer trust and long-term brand damage.

  • Operational Disruptions: Data theft, fraud, and service disruptions affecting business continuity and revenue.


Building a Robust API Security Framework


Organizations must prioritize API security to mitigate these risks and protect their digital assets. Key components of a robust API security framework include:

  • API Discovery and Inventory: Identifying and cataloging all APIs, including shadow APIs, third-party APIs, and legacy systems.

  • API Posture Governance: Continuously assessing and monitoring the security posture of APIs, identifying potential risks, and implementing improvements.

  • API Threat Protection: Detecting and preventing API attacks, including those from the OWASP Top 10 and complex business logic threats.

  • API Vulnerability Management: Identifying and addressing API vulnerabilities before they can be exploited.

  • API Compliance: Ensuring adherence to regulatory frameworks and standards, and validating compliance with security best practices.


The FTC's settlement with GoDaddy serves as a critical reminder of the importance of robust API security. By implementing comprehensive security measures, organizations can protect sensitive data, maintain customer trust, and avoid regulatory penalties. As the digital landscape continues to evolve, prioritizing API security will be essential for safeguarding business operations and ensuring long-term success.

bottom of page