• 7 Posts
  • 68 Comments
Joined 2 years ago
cake
Cake day: July 4th, 2023

help-circle

  • If for example the server is actually a computer in the LAN and maybe it’s also his media server and his backup server then potentially any compromise could lead to his personal information leaked and or other computers in the LAN compromised.

    So what could actually happen? His personal photos and passwords and accounts can be leaked or taken over. He could be spied on by accessing his webcam. A lot of things could go wrong.

    You are right. Learning by doing is awesome. Just be sure to do it in a safe way. Get a VPC. Do it there. No personal information, no access to other services. Just this service, just for this purpose. Worst case scenario, if it’s taken over, the only thing that’s harmed is the forum itself. Which is not the end of the world, I’m guessing.




  • Don’t do it.

    Hosting a public service with no real knowledge of security can only end badly.

    Get a vpc, do it there, learn from mistakes.

    It’s more than just HTTPS, you also need proper authentication, regular updates, emergency updates for critical vulnerabilities, ideally some sort of monitoring to detect potential misuse of the service or any escalations from the service to the OS.

    Ask yourself this: If this was your first time driving a car, would you rather do it in an empty parking lot where at worst you will damage the car. Or would you rather do it in a busy street where at worst you can kill someone?




  • MTK@lemmy.worldtoSelfhosted@lemmy.worldSIEM
    link
    fedilink
    English
    arrow-up
    4
    ·
    7 days ago

    I suggest skipping the devops part and instead starting with a course. If you go with setting it up you will probably spend 95% of the time doing devops and not security (which is usually the client of the devops team that maintains the SIEM)


  • IP based blocking is complicated once you are big enough or providing service to users is critical.

    For example, if you are providing some critical service such as health care, you cannot have a situation where a user cannot access health care info without hard proof that they are causing an issue and that you did your best to not block the user.

    Let’s say you have a household of 5 people with 20 devices in the LAN, one can be infected and running some bot, you do not want to block 5 people and 20 devices.

    Another example, double NAT, you could have literally hundreds or even thousands of people behind one IP.