Comparison Overview
BITMARCK

BITMARCK
Kruppstraße 64, Essen, Nordrhein-Westfalen, DE, 45145
Last Update: 30/03/2026
As a managed service provider for the IT market of statutory health insurance, BITMARCK furthers digitalization of this sector as well as innovative solutions and services for its customers. 85 percent of all German, statutory health insurances are customers of BITMARCK...

Amazon Web Services (AWS)
410 Terry Ave N, Seattle, 98019, US
Last Update: 14/09/2026
Launched in 2006, Amazon Web Services (AWS) began exposing key infrastructure services to businesses in the form of web services -- now widely known as cloud computing. The ultimate benefit of cloud computing, and AWS, is the ability to leverage a new business model and...
Compliance Ranges Comparison

BITMARCK







Amazon Web Services (AWS)






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for BITMARCK in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Amazon Web Services (AWS) has 2424.27% more incidents than the average of all companies with at least one recorded incident.
Incident History - BITMARCK (X = Date, Y = Severity)
BITMARCK cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amazon Web Services (AWS) (X = Date, Y = Severity)
Amazon Web Services (AWS) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BITMARCK

Amazon Web Services (AWS)
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)