91
For users with public facing services: How does the current explosion of AI-discovered vulnerabilities affect your threat model and willingness to be public facing? (lemmy.ml)
submitted 2 weeks ago by to c/selfhosted@lemmy.world
63 comments fedilink hide all child comments
 

PHP, TLS, etc.. We appear to be facing a tsunami of vulnerabilities being discovered in record time. Further, the window to act on these vulnerabilities has basically closed to zero; hackers' tools now automatically fold the very latest vulnerabilities into their botnets within minutes/hours of discovery. I have always been extremely reluctant to expose any of my services - even with the latest and greatest security tools. My choice to stay totally within the confines of tailscale seems vindicated given this week's news. How are you all taking this?

https://pwn.watch/

you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 2 weeks ago (2 children)

I only have a VPN endpoint exposed. If I need to access any of my web services I simply VPN in and away I go.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 5 points 2 weeks ago

    Tailscale is the super easy version of this. Otherwise make sure your containers don’t have root etc. block inter container networking as much as you can. Lots of relatively simple things work unless you’re actually an interesting target.

  • permalink
  • fedilink
  • source
  • parent