# Using Security Certificates Kaseya uses an integrated application firewall which monitors all web-based communication going to and from the Windows server that Kaseya is hosted on. This provides an added level of security by enabling Kaseya to log and potentially block malicious activity or application security attacks. Kaseya strongly recommends that all web-based communication be encrypted using a security certificate. If you have visited Google or a financial services website, you will notice the “HTTPS” and a lock icon in your browser’s address bar to indicate the communication between your browser and the website is encrypted. Kaseya uses TLS for all secured HTTP and WebSocket connections. To enable secure web traffic, the Kaseya Application Firewall needs a security certificate to be imported. The security certificate and its corresponding private key allow for communication to be encrypted and prove the identity of the server. For detailed instructions on how to configure the Kaseya Application Firewall with a security certificate, please read the options below and click the link applicable to your environment to read the corresponding knowledge base article: You already have a security certificate in Microsoft IIS that you wish to export and use in the Kaseya Application Firewall. See Detailed Instructions... The Kaseya Server installation wizard includes a step for applying the exported security certificate to the Kaseya Server. You don’t have a security certificate and want to purchase one from a trusted certificate authority—Verisign, Thawte, DigiCert, etc… —to use in the Kaseya Application Firewall. See Detailed Instructions... You want to create a self-signed security certificate to use in the Kaseya Application Firewall. See Detailed Instructions...
Topic 18015: Send Feedback. Download a PDF of this online book from the first topic in the table of contents. Print this topic.