we arent alone

[viss@mastodon.social]

we arent alone

Counting the waves of tech industry BS from blockchain to AI

Opinion: After decades in the trenches, this engineer is done with hype cycles

(www.theregister.com)

[da_667@infosec.exchange]

@Viss FINALLY.

[da_667@infosec.exchange]

@Viss yo, we sure these dudes are working in cybersecurity

[viss@mastodon.social]

@da_667 supposedly the guy who was interviewed is ex redhat?

[viss@mastodon.social]

@da_667 yup, exactly

[coreysnipes@hachyderm.io]

@da_667

[fritzadalis@infosec.exchange]

@Viss @da_667
Not yet...

[viss@mastodon.social]

@thomas_klopf i've done probably 3 dozen assessments for companies that are running k8s. this article speaks the truth. ive seen maybe one? two? "properly configured" k8s installs. the rest are .. well, not great. its bureaucracy for the sake of bureaucracy. nobody is using it right, and it creates way way way more problems than it solves.

then there's shit like moltbot/moltbook, which is just .. building a house out of dynamite

[rx13@infosec.exchange]

@da_667 @Viss
My only point of disagreement is that visibility reduction on bare metal is difficult to do at scale with active operations team; containers do add something in reducing immediately available real estate for exploitation (if configured well), that would otherwise be limitations that will vary app to app on the same device (Assuming you run multiple services on the same device).

Having had to lockdown systems and limit access to binaries, etc, etc, it can be done, but containers do make that easier to some extent (if similarly well configured).

Not that it's a replacement for the former, but it can be a good tool to help in the matter.

[kallisti@infosec.exchange]

@da_667 @Viss@mastodon.social I feel heard

[da_667@infosec.exchange]

@kallisti you're not alone.

[lproven@social.vivaldi.net]

@stuartl @Viss *Tips virtual hat*

[viss@mastodon.social]

@lproven @stuartl i think our brains may be touching