home.social

Search

243 results for “ghostinthenet”

  1. For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. github.com/ghostinthenet/l2vpn #MTPC #NetEng

  2. For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. github.com/ghostinthenet/l2vpn #MTPC #NetEng

  3. For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, , and files can be found here. github.com/ghostinthenet/l2vpn

  4. For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. github.com/ghostinthenet/l2vpn #MTPC #NetEng

  5. For anyone interested in my “Scalable and Secure Self-Serve RouterOS Remote Management” presentation at the MikroTik Professionals Conference in Prague, the slide deck, #Docker, and #ContainerLab files can be found here. github.com/ghostinthenet/l2vpn #MTPC #NetEng

  6. From Tech Field Day - Networking Field Day 38 7/9-7/10:

    NEW: Enterprises Shouldn't Be Outsourcing Their IT Anymore 🎧🎙️

    Watch ➡️ buff.ly/aFsxzaB

    Enterprise networks are complex and fully outsourcing ops doesn’t always guarantee better results.

    @networkingnerd
    @chrisgrundemann
    @avalonhawk
    @ghostinthenet

    #TFDPodcast #NFD38

  7. @ghostinthenet last I read, they’re saying 7 years now 😭 hope everyone can handle me forgetting #allTheThings for 7 more years 🤣 I guess it won’t seem different at least..

  8. Wow. Fifteen years since I became a founding member of the #FNS. Great experiences, great people, dubious networking. flatnetworksociety.com/ #NetEng

  9. Auditor: Can you send a screenshot of the access VPN timeouts so we can demonstrate policy compliance?
    Me: (Sends relevant portions of the configuration.)
    Them: This is a text file. We need a screenshot.
    Me: (Sends screenshot of my terminal session showing the relevant portions of the configuration.)

  10. Auditor: Can you send a screenshot of the access VPN timeouts so we can demonstrate policy compliance?
    Me: (Sends relevant portions of the configuration.)
    Them: This is a text file. We need a screenshot.
    Me: (Sends screenshot of my terminal session showing the relevant portions of the configuration.)
    #InfoSec #NetEng #MaliciousCompliance

  11. Auditor: Can you send a screenshot of the access VPN timeouts so we can demonstrate policy compliance?
    Me: (Sends relevant portions of the configuration.)
    Them: This is a text file. We need a screenshot.
    Me: (Sends screenshot of my terminal session showing the relevant portions of the configuration.)
    #InfoSec #NetEng #MaliciousCompliance

  12. Auditor: Can you send a screenshot of the access VPN timeouts so we can demonstrate policy compliance?
    Me: (Sends relevant portions of the configuration.)
    Them: This is a text file. We need a screenshot.
    Me: (Sends screenshot of my terminal session showing the relevant portions of the configuration.)
    #InfoSec #NetEng #MaliciousCompliance

  13. Auditor: Can you send a screenshot of the access VPN timeouts so we can demonstrate policy compliance?
    Me: (Sends relevant portions of the configuration.)
    Them: This is a text file. We need a screenshot.
    Me: (Sends screenshot of my terminal session showing the relevant portions of the configuration.)
    #InfoSec #NetEng #MaliciousCompliance

  14. We have dozens of relatively simple methods to secure Internet traffic, but we’re often reduced to “just open access through your firewalls from this huge list of source addresses” because too many folks can’t be arsed to do any of those. Keeping it simple is •not• about moving the complexity into the customer’s realm of responsibility. #NetEng #InfoSec

  15. We have dozens of relatively simple methods to secure Internet traffic, but we’re often reduced to “just open access through your firewalls from this huge list of source addresses” because too many folks can’t be arsed to do any of those. Keeping it simple is •not• about moving the complexity into the customer’s realm of responsibility. #NetEng #InfoSec

  16. We have dozens of relatively simple methods to secure Internet traffic, but we’re often reduced to “just open access through your firewalls from this huge list of source addresses” because too many folks can’t be arsed to do any of those. Keeping it simple is •not• about moving the complexity into the customer’s realm of responsibility.

  17. We have dozens of relatively simple methods to secure Internet traffic, but we’re often reduced to “just open access through your firewalls from this huge list of source addresses” because too many folks can’t be arsed to do any of those. Keeping it simple is •not• about moving the complexity into the customer’s realm of responsibility. #NetEng #InfoSec

  18. We have dozens of relatively simple methods to secure Internet traffic, but we’re often reduced to “just open access through your firewalls from this huge list of source addresses” because too many folks can’t be arsed to do any of those. Keeping it simple is •not• about moving the complexity into the customer’s realm of responsibility. #NetEng #InfoSec

  19. Cloud services, data security risk, and limitation of liability clauses are a bit of a perfect storm. Too many of us use the services because they’re accessible, but we’re often blindly trusting that they will (or can - see CLOUD/NSL considerations) keep our data secure, and don’t consider that we have little to no recourse when they don’t. As always, #security and #sovereignty hold no priority over convenience… until it’s too late. #InfoSec

  20. I think I’ve been in this industry for too long. I searched for a synopsis this morning and accidentally typed “synoptics” instead. Last week I was teaching the NATO phonetic alphabet and taught “unicorn” instead of “uniform.” #NetEng #SiliconValley

  21. I think I’ve been in this industry for too long. I searched for a synopsis this morning and accidentally typed “synoptics” instead. Last week I was teaching the NATO phonetic alphabet and taught “unicorn” instead of “uniform.” #NetEng #SiliconValley

  22. I think I’ve been in this industry for too long. I searched for a synopsis this morning and accidentally typed “synoptics” instead. Last week I was teaching the NATO phonetic alphabet and taught “unicorn” instead of “uniform.”

  23. I think I’ve been in this industry for too long. I searched for a synopsis this morning and accidentally typed “synoptics” instead. Last week I was teaching the NATO phonetic alphabet and taught “unicorn” instead of “uniform.” #NetEng #SiliconValley

  24. I think I’ve been in this industry for too long. I searched for a synopsis this morning and accidentally typed “synoptics” instead. Last week I was teaching the NATO phonetic alphabet and taught “unicorn” instead of “uniform.” #NetEng #SiliconValley

  25. "SD-WAN" (over MPLS no less!) with IPSec tunnels (not transports!), hard static routes for link monitoring, and floating static routes for tunnel failover... because that's less complicated than using a routing protocol. #NetEng #BangHeadHere

  26. "SD-WAN" (over MPLS no less!) with IPSec tunnels (not transports!), hard static routes for link monitoring, and floating static routes for tunnel failover... because that's less complicated than using a routing protocol. #NetEng #BangHeadHere

  27. "SD-WAN" (over MPLS no less!) with IPSec tunnels (not transports!), hard static routes for link monitoring, and floating static routes for tunnel failover... because that's less complicated than using a routing protocol.