To better protect your Bynder portal and ensure a safer user experience, we have integrated AWS Web Application Firewall (AWS WAF) into Bynder. Discover how this helps keep your portal secure.
How to Enable AWS Web Application Firewall?
AWS WAF is automatically enabled for clients using our CDN. No additional configuration is required. If you are not yet on our CDN, please connect with your Customer Success Contact for more information.
What is AWS Web Application Firewall?
AWS Web Application Firewall (AWS WAF) analyzes all incoming traffic on our servers in real time. It protects against common attacks, such as SQL injections, DDoS attacks, and Cross-Site Scripting (XSS), which could compromise security and impact the availability of our systems. Read more about AWS Web Application Firewall here.
Top 10 Security Risks Protected by AWS WAF
AWS WAF shields your portal from the top 10 security risks. This list is compiled by the Open Web Application Security Project (OWASP). Learn more about OWASP’s security risks here.
- Injections
- Broken Authentication
- Sensitive Data Exposure
- XML External Entities (XXE)
- Broken Access Control
- Security Misconfiguration
- Cross-Site Scripting (XSS)
- Insecure Deserialization
- Using Components with Known Vulnerabilities
- Insufficient Logging & Monitoring
- Additionally, AWS WAF blocks excessive resource usage by enforcing an API rate limit, ensuring seamless performance for all customers.
API Rate Limiting
API rate limiting is a common practice that ensures consistent performance and service levels for all customers. It prevents excessive consumption of API resources, allowing you to use our API seamlessly.
We allow up to 4,500 requests from a single IP address within five minutes. Once this limit is reached, any additional requests will be blocked, and you will receive an HTTP 429 (Too Many Requests) error via the API. After five minutes of inactivity from your IP address, AWS WAF will lift the block, and you can resume sending API requests.
Updated