#vendorlockin — Public Fediverse posts

Today it is Mythos. Tomorrow it will be something else.

The pattern stayvendorlockin #securitystrategy #appsec #operationalresiliencempanies need urgency to position themselves.

Everyone wants to attach themselves to the next big wave and present themselves as the answer.

Real organizational readiness is not about pushing AI into every layer because the current panic cycle says so. The practical test for any change is much simpler:

• Does it strengthen existing tools and workflows?

• Does it preserve model and vendor optionality?

• Does it reduce backlog and repetitive operational drag?

• Does it reduce attack surface by removing software, access, and exposure you do not need?

• Does it reinforce the boring fundamentals like inventory, patching, least privilege, segmentation, and recovery?

Without those checks, you are mostly just trading places. One dependency gets swapped for another. One vendor stack gets replaced by another. One kind of complexity becomes another. Very little materially improves.

Most of the time, we just kick the ball a few months further down the road and call it progress.

I wrote about many of these ideas in my pragmatic guide:
https://cyfinoid.com/a-pragmatic-guide-to-being-mythos-ready/

#securitystrategy #appsec #operationalresiliencempanies #cybersecurity #aisecurity #attacksurfacereduction #vendorlockin #operationalresilience

Today it is Mythos. Tomorrow it will be something else.

The pattern stayvendorlockin #securitystrategy #appsec #operationalresiliencempanies need urgency to position themselves.

Everyone wants to attach themselves to the next big wave and present themselves as the answer.

Real organizational readiness is not about pushing AI into every layer because the current panic cycle says so. The practical test for any change is much simpler:

• Does it strengthen existing tools and workflows?

• Does it preserve model and vendor optionality?

• Does it reduce backlog and repetitive operational drag?

• Does it reduce attack surface by removing software, access, and exposure you do not need?

• Does it reinforce the boring fundamentals like inventory, patching, least privilege, segmentation, and recovery?

Without those checks, you are mostly just trading places. One dependency gets swapped for another. One vendor stack gets replaced by another. One kind of complexity becomes another. Very little materially improves.

Most of the time, we just kick the ball a few months further down the road and call it progress.

I wrote about many of these ideas in my pragmatic guide:
https://cyfinoid.com/a-pragmatic-guide-to-being-mythos-ready/

#securitystrategy #appsec #operationalresiliencempanies #cybersecurity #aisecurity #attacksurfacereduction #vendorlockin #operationalresilience

Today it is Mythos. Tomorrow it will be something else.

The pattern stayvendorlockin #securitystrategy #appsec #operationalresiliencempanies need urgency to position themselves.

Everyone wants to attach themselves to the next big wave and present themselves as the answer.

Real organizational readiness is not about pushing AI into every layer because the current panic cycle says so. The practical test for any change is much simpler:

• Does it strengthen existing tools and workflows?

• Does it preserve model and vendor optionality?

• Does it reduce backlog and repetitive operational drag?

• Does it reduce attack surface by removing software, access, and exposure you do not need?

• Does it reinforce the boring fundamentals like inventory, patching, least privilege, segmentation, and recovery?

Without those checks, you are mostly just trading places. One dependency gets swapped for another. One vendor stack gets replaced by another. One kind of complexity becomes another. Very little materially improves.

Most of the time, we just kick the ball a few months further down the road and call it progress.

I wrote about many of these ideas in my pragmatic guide:
https://cyfinoid.com/a-pragmatic-guide-to-being-mythos-ready/

#securitystrategy #appsec #operationalresiliencempanies #cybersecurity #aisecurity #attacksurfacereduction #vendorlockin #operationalresilience

Today it is Mythos. Tomorrow it will be something else.

The pattern stayvendorlockin #securitystrategy #appsec #operationalresiliencempanies need urgency to position themselves.

Everyone wants to attach themselves to the next big wave and present themselves as the answer.

Real organizational readiness is not about pushing AI into every layer because the current panic cycle says so. The practical test for any change is much simpler:

• Does it strengthen existing tools and workflows?

• Does it preserve model and vendor optionality?

• Does it reduce backlog and repetitive operational drag?

• Does it reduce attack surface by removing software, access, and exposure you do not need?

• Does it reinforce the boring fundamentals like inventory, patching, least privilege, segmentation, and recovery?

Without those checks, you are mostly just trading places. One dependency gets swapped for another. One vendor stack gets replaced by another. One kind of complexity becomes another. Very little materially improves.

Most of the time, we just kick the ball a few months further down the road and call it progress.

I wrote about many of these ideas in my pragmatic guide:
https://cyfinoid.com/a-pragmatic-guide-to-being-mythos-ready/

#securitystrategy #appsec #operationalresiliencempanies #cybersecurity #aisecurity #attacksurfacereduction #vendorlockin #operationalresilience

Today it is Mythos. Tomorrow it will be something else.

The pattern stayvendorlockin #securitystrategy #appsec #operationalresiliencempanies need urgency to position themselves.

Everyone wants to attach themselves to the next big wave and present themselves as the answer.

Real organizational readiness is not about pushing AI into every layer because the current panic cycle says so. The practical test for any change is much simpler:

• Does it strengthen existing tools and workflows?

• Does it preserve model and vendor optionality?

• Does it reduce backlog and repetitive operational drag?

• Does it reduce attack surface by removing software, access, and exposure you do not need?

• Does it reinforce the boring fundamentals like inventory, patching, least privilege, segmentation, and recovery?

Without those checks, you are mostly just trading places. One dependency gets swapped for another. One vendor stack gets replaced by another. One kind of complexity becomes another. Very little materially improves.

Most of the time, we just kick the ball a few months further down the road and call it progress.

I wrote about many of these ideas in my pragmatic guide:
https://cyfinoid.com/a-pragmatic-guide-to-being-mythos-ready/

#securitystrategy #appsec #operationalresiliencempanies #cybersecurity #aisecurity #attacksurfacereduction #vendorlockin #operationalresilience

Sehr schön. Andree hat in beiden Büchern aufeinander aufbauend die Fakten strukturiert vorgeführt zum Themenkomplex #DigitaleSouveränität, #Medienregulierung, #VendorLockin und #Monopolisierung, die Trump, Thiel, Musk, US TechBros ausnutzen, um damit Demokratie durch #Deregulierung zu vernichten. Für den maximalen Profit in Milliardenhöhe. Und er zeigt auf, dass dies seit Jahren schon maximal etabliert wurde!

Andree vermittelt eine klare Agenda zu Ursachen und Auswirkungen...

Finding a sleek, distraction free #markdown editor for #Android is rough, especially when paired with a cloud storage provider that isn't #Google.

My candidates were #OpenNote and #Quilpad, but both take away power from the user by preventing them from managing their own files.

Both refuse to work with the Android cloud provider backend, to a point where I can't even import my MD files from #Jottacloud.

One has experimental support for #Nextcloud tho, which smells like #vendorlockin.

#PubliekeWaarden in het #onderwijs zijn essentieel. Hoe komen die tot uiting in de #IT die wordt gebruikt op scholen? Wat zijn de risico's van oncontroleerbare, #proprietary software? Hoe zit het met #privacy van #leerlingen en #vendorlockin van #scholen?

Welke rol kan vrije- #opensource software spelen in #educatie?

Geert-Jan en @remark gaven een #analyse met #oplossingsrichting op #FOSDEM.

Sterk aanbevolen, zeker aan degenen die actief zijn in het onderwijs:

https://video.fosdem.org/2025/ud6215/fosdem-2025-6042-public-values-and-foss-for-education.av1.webm

#FOSS