Static credentials with passwords written into a firewall’s code. What could go wrong?

  • sylver_dragon@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    ·
    7 days ago

    This is a good example of why a zero trust network architecture is important. This attack would require the attacker to be able to SSH to the management interface of the device. Done right, that interface will be on a VLAN which has very limited access (e.g. specific IPs or a jumphost). While that isn’t an impossible hurdle for an attacker to overcome, it’s significantly harder than just popping any box on the network. People make mistakes all the time, and someone on your network is going to fall for a phishing attack or malicious redirect or any number of things. Having that extra layer, before they pop the firewall, gives defenders that much more time to notice, find and evict the attacker.

    Also, Whiskey, Tango, Foxtrot Cisco?

    • horse_battery_staple@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      7 days ago

      That layered security should not be assumed though, thus the issue with hard coded passwords on a firewall. I’d understand for a downstream managed switch. Not a firewall though…bad form and lazy implementation. In my opinion.

      • sylver_dragon@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        7 days ago

        Ya, absolutely. My point was that, we shouldn’t assume that vendors are doing things right all the time. So, it’s important to have those layered defense, because vendors do stupid stuff like this.