Using SSLv3 protocol to communicate with Site24x7 servers
Secure Socket Layer version 3 (SSLv3) is a security protocol that is used to secure application protocols such as HTTP, FTP, SIP, SMTP, NNTP, and XMPP. SSLv3 has "Poodle" vulnerability which makes it susceptible to security threats such as man in the middle attacks and as such any requests made to our server using this protocol will be discarded.
By default, all our agents use Transport Layer Security (TLS) protocol for all communications. If your agent isn't already configured to use TLS protocol, you can force all HTTPS requests to use TLS or any other protocol by specifying them as -Dhttps.protocols in JVM arguments.
Example: -Dhttps.protocols=TLSv1 -javaagent:{full_path}/apminsight-javaagent.jar
Related Articles
Monitor and validate DNS IP changes using regex
DNS administrators often monitor their DNS servers to detect changes in domain resolution and ensure IP mappings remain secure and accurate. Problem When your organization adds or modifies an IP address for your domain name, it’s critical to: Be ...
How do I check if URL redirection works correctly using the Website Monitor?
A webpage can be made available from more than a single web address using URL redirection. Most redirects are automated and it becomes difficult to track if the redirection works in a specific way. This can be verified using website monitoring in ...
Validating sender email using DKIM authentication
What is DKIM? DomainKeys Identified Mail (DKIM) is an advanced authentication method used widely by email service providers to verify the email from the point of its origin by validating the email sender. It allows the email senders to authenticate ...
Compare our various methodologies for Website Monitoring
Get to know Site24x7 monitors better and choose the one that best fits your monitoring needs. Compare the functionality of the following monitors: Website Monitoring Webpage Speed (Browser) Web Transaction Monitoring Web Transaction (Browser) SSL/TLS ...
Troubleshooting false positive alerts in monitoring
Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...