Guardian Communications

I understand that Guardian uses FTP do download items through Guardian links or KBA article links (MS security updates, hotfixes etc...)

What communications ports are used to download via FTP?

What protocol is used to upload the Sure Service Registration file back to Guardian?  Is this an FTP upload?  What ports are required for this communication to work?

What is the timing for converting Guardian to SFTP (secure FTP)?

 

My corporate IT is tightening firewall rules across the board.  I had to request a firewall rule deviation to allow FTP traffic from Guardian to allow download traffic for updates and hotfixes.  This is only a temporary fix with an expiration date.

 

 

  • Hi Robert! , our Guardian Support Program Manager, is gathering more detailed answers to your questions, but I wanted to give you a few responses before the Labor Day weekend (and then Bob or perhaps also can follow up with more detail).

    We’re using the default FTP port: 21

    I think we plan to release our Secure FTP solution by the end of the year.

    More answers coming soon!
  • Hi Robert, to answer your questions, (in addition to what Jocelyn mentioned)...

    It is port 21, (by default).

    Typically customers will run the Registration Utility and then save it to a USB stick, (or put it on a shared drive), and send it to Guardian via the Guardian website. We are using https and not FTP for registration file upload.

    We will have Secure FTP in place by November 2015.