Suggestions
Mehmet Özer Metin
Chief Technology Innovation Officer
Mehmet Özer Metin is the Chief Technology Innovation Officer at Comodo, a cybersecurity company.1 He has over 20 years of engineering and product management experience in the field.1
Professional Background
Metin's expertise lies in cybersecurity, particularly in areas such as antivirus and EDR (Endpoint Detection and Response) technologies.3 He holds a Ph.D., for which he made a significant contribution to the DTI (Diffusion Tensor Imaging) group.7
Current Role and Responsibilities
As the Chief Technology Innovation Officer at Comodo, Metin is involved in various aspects of cybersecurity:
- Technology Leadership: He provides insights on cybersecurity trends and incidents, such as the recent CrowdStrike tech outage.5
- Product Development: Metin is likely involved in developing and improving Comodo's cybersecurity solutions.
- Industry Analysis: He shares his thoughts on industry challenges, such as the risks associated with cybersecurity vendors' update cycles.6
Recent Activities
Metin has been active in discussing and addressing current cybersecurity issues:
- In July 2024, he posted about recurring patterns in cybersecurity, suggesting a cyclical nature to certain events or challenges in the field.2
- He has been involved in providing solutions for organizations affected by the CrowdStrike incident, particularly focusing on remediation for AWS and Azure environments.4
- Metin has participated in discussions about the effects of the CrowdStrike tech outage, offering suggestions for improved cybersecurity practices.5
Mehmet Özer Metin's extensive experience and current role position him as a thought leader in the cybersecurity industry, particularly in the areas of endpoint protection and cloud security.
Highlights
While larger corporations have recovered from the recent Crowdstrike incident, we know that some are still struggling with recovery. Collaborating with Rahul Jadhav, we developed an automated recovery script to detach relevant volumes, delete the corrupted Crowdstrike "channel files" from instance and attach them again for AWS and Azure workloads. You can find the script here: https://lnkd.in/eADQEy8Q
Before using our script, please check the recovery suggestions from Azure and AWS: https://lnkd.in/eTnjP4Rv
https://lnkd.in/eBZiPKP9
If these suggestions do not resolve your issue, you can use our remediation scripts. We are also planning to expand this solution to GCP. Contributions are welcome!
I feel for the Crowdstrike engineers facing significant burdens and stress over the weekend. As someone who manages engineering on my side, I understand the challenges of continuously releasing new versions while maintaining stable and high-quality endpoint agents. This task is vastly different from typical SaaS product release cycles. Each release brings unknown challenges in the field due to thousands of different configurations and customer environments, and we only get one chance to get it right.
However, thanks to our unique architecture, we don't need to chase every emerging threat with a code update. Our containment technology allows us to protect endpoints without relying solely on detection. By doing quarterly major releases for our endpoint agents, we ensure ample time to properly test and validate across various configurations. In this post, I summarize our release methodology and explain how we mitigate such pitfalls.
