# CrowdStrike is a Harsh Reminder of the Danger of Third-Party Clients

**URL:** <https://discuss.pomerium.com/t/crowdstrike-is-a-harsh-reminder-of-the-danger-of-third-party-clients/389>\
**Category:** blog\
**Tags:** infrastructure\
**Created:** [August 5, 2024, 5:29pm UTC](https://discuss.pomerium.com/t/crowdstrike-is-a-harsh-reminder-of-the-danger-of-third-party-clients/389 "2024-08-05T17:29:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CMo](https://avatars.discourse-cdn.com/v4/letter/c/d78d45/32.png) [@CMo](https://discuss.pomerium.com/u/CMo)\
**Post date:** [August 5, 2024, 5:29pm UTC](https://discuss.pomerium.com/t/crowdstrike-is-a-harsh-reminder-of-the-danger-of-third-party-clients/389/1 "2024-08-05T17:29:43Z")

</div>

> **[CrowdStrike is a Harsh Reminder of the Danger of Third-Party Clients](https://www.pomerium.com/blog/crowdstrike-bsod-incident)**
>
> The true lesson from the CrowdStrike BSOD debacle: avoid third-party clients

- Clients suck to maintain and are unreliable
- Auto-updates risk another incident
- Closed-source software does not allow for verification