• 9 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle













  • lungdart@lemmy.catoSelfhosted@lemmy.worldAnother good reason not to open port 22
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    11 months ago

    Moving the port doesn’t reduce attack surface. It’s the same amount of surface.

    Tailscale is a bit controversial because it requires a 3rd party to validate connections, a 3rd party that is a large target for threat actors, and is reliant on profitability to stay online.

    I would recommend a client VPN like wireguard, or SSH being validated using signed keys against a certificate authority your control, with fail2ban.


  • This is not true and bad security practice.

    There are exploits that can be installed without a mistake made on the users part, the user can make a mistake, and almost every user downloads and open files regularly.

    Windows is less secure than the other options, but the other options are not impenetrable. The biggest botnets are made of Linux IoT devices, and nobody opened the wrong email on they’re thermostat…

    What a virus scanner will do is check your filesystem and possibly program memory for known footprints. A tool like this can save you from becoming a node on a botnet or being crypto locked. More importantly, if you work from home it can save your company from this issue as well!


  • lungdart@lemmy.catoSelfhosted@lemmy.worldHave I been DoS'd?
    link
    fedilink
    English
    arrow-up
    25
    ·
    11 months ago

    Sounds like you were out of resources. That is the goal of a DoS attack, but you’d need connection logs to detect if that was the case.

    DDoS attacks are very tricky to defend. (Source: I work in DDoS defence). There’s two sections to defense, detection and mitigation.

    Detection is very easy, just look at packets. A very common DDoS attack uses UDP services to amplify your request to a bigger response, but then spoof your src ip to the target. So large amounts of traffic is likely an attack, out of band udp traffic is likely an attack. And large amount of inband traffic could be an attack.

    Mitigation is trickier. You need something that can handle a massive amount of packet inspection and black holing. That’s done serious hardware. A script kiddie can buy a 20Gbe/1mpps attack with their moms credit card very easily.

    Your defence options are a little limited. If your cloud provider has WAF, use it. You may be able to get rules that block common botnets. Cloudflare is another decent option, they’ll man in the middle your services, and run detection and mitigation on all traffic. They also have a decent WAF.

    Best of luck!




  • Very common.

    Don’t feel pressured to approve anything you don’t want to, but still be chill. It’s just work after all. (This duality takes years to figure out, but if you can, you’ll be very valuable)

    Get the PM involved. Bring it up in retro and stand up.

    Examples.

    “I don’t feel this is PR is up to our company standards. Here’s a link to the document. Specifically tests are breaking, coverage is reduced, and your using global variables. If you need help with quality we can code pair next sprint or if I finish my tasks early. Let me know”

    “Just a reminder that we have 3 PRs with needs work sitting in the queue. If you’re not able to finish them before the end of the sprint, let the scrum master/PM know in case it’s a high priority”

    “We’ve all signed off on a standards guideline, and lots of PRs are falling short. Either we need more training time each sprint to reach it, or were going to have to officially reduce our standards. Let me know which one the CTO prefers”