As someone in that field, I can assure you everyone is having to do a lot more CyberSecurity than they used to.
While there is a lot of AI slop out there, it’s also having a huge impact on the cyber security front, in that it's finding vulnerabilities that are many years old and also brand new ones, faster than ever before. This makes it harder for the good guys to keep up. It’s definitely important to be mindful of security these days.
I actually have been using claude to go through all my old projects and review from a security perspective.
It flags a heap of things that I never considered, mainly because a lot of my projects were ad-hoc solutions to various issues that were written in a hurry and never intended to be visible to the general internet. But it also has been suggesting architectural and robustness changes that have some value, as a lot of stuff I wrote grew organically and weren't structured particularly well for future growth.
What do you mean by this? Like, MTLS or requiring people to install client certificates in their browsers, or installing certificates in some other client application. Or something else?
And who are/own the clients in question? These aren't B2C sort of customers, are they?
Just fiddling with the console to see if I can get onto panels I shouldn't. Making bool return funcs always go true and seeing the results. Like, the Fifa hack where they made the role checks on the client, not the server.
Ah. Ok, yeah. That makes sense. I just wanted to make sure you weren't advocating for doing more security checks on the client and thinking that would improve security at all. But I see you were saying quite the opposite.
7 Comments
WhatsHerBucket@lemmy.world · 13 pts · 20d
As someone in that field, I can assure you everyone is having to do a lot more CyberSecurity than they used to.
While there is a lot of AI slop out there, it’s also having a huge impact on the cyber security front, in that it's finding vulnerabilities that are many years old and also brand new ones, faster than ever before. This makes it harder for the good guys to keep up. It’s definitely important to be mindful of security these days.
HrMoon@lemmy.world · 8 pts · 20d
you have to selfhost and encrypt everything :)
jchaven@social.sdf.org · 5 pts · 20d
@HrMoon
...and download your tools now - before you need them and before something happens to them (see TrueCrypt).
@Gonzako
dgriffith@aussie.zone · 4 pts · 19d
I actually have been using claude to go through all my old projects and review from a security perspective.
It flags a heap of things that I never considered, mainly because a lot of my projects were ad-hoc solutions to various issues that were written in a hurry and never intended to be visible to the general internet. But it also has been suggesting architectural and robustness changes that have some value, as a lot of stuff I wrote grew organically and weren't structured particularly well for future growth.
TootSweet@lemmy.world · 1 pts · 20d
What do you mean by this? Like, MTLS or requiring people to install client certificates in their browsers, or installing certificates in some other client application. Or something else?
And who are/own the clients in question? These aren't B2C sort of customers, are they?
Gonzako@lemmy.world · 2 pts · 20d
Just fiddling with the console to see if I can get onto panels I shouldn't. Making bool return funcs always go true and seeing the results. Like, the Fifa hack where they made the role checks on the client, not the server.
TootSweet@lemmy.world · 2 pts · 19d
Ah. Ok, yeah. That makes sense. I just wanted to make sure you weren't advocating for doing more security checks on the client and thinking that would improve security at all. But I see you were saying quite the opposite.