• bonn2@lemm.ee
    link
    fedilink
    arrow-up
    33
    ·
    edit-2
    1 year ago

    There could, in theory, be a malicious machine on the internal network that was previously infected, which is now acting as command and control. So if you didn’t know which one it was…

      • blabber6285@sopuli.xyz
        link
        fedilink
        arrow-up
        10
        ·
        1 year ago

        That’s generally a good idea, however, there can be reasons not to do it.

        The device could be infected in a way that it won’t turn on again.

        You might have an isolated management network that allows you to monitor the device and traffic (naturally ripping all cables also disconnects the management network).

        And whatnot. But generally I agree.

        • averagedrunk
          link
          fedilink
          arrow-up
          7
          arrow-down
          1
          ·
          1 year ago

          You two are overlooking the most important thing. It might be fun to crazily rip out the cables then make a junior guy go trace and repatch it all. The opportunity to legitimately do that doesn’t come along often.