veridian.com.au
Security rating · scale 0–950 · grades A–F
Veridian Solutions's UpGuard security rating is C (565 / 950), which is fair. 14 of 52 external checks are currently failing, mostly in Encryption and Website Security.
No failing checks in Data leakage, IP/Domain Reputation, and Vulnerability Management.
Failing checks: Secure cookies not used; CSP is not implemented; HttpOnly cookies not used; and 11 more.
veridian.com.au
UpGuard continuously monitors Veridian Solutions's externally observable security posture across Website Security, Email, Network, DNS, Encryption, Data leakage, IP/Domain Reputation, and Vulnerability Management. The rating reflects only what can be verified from outside the organization. It is not an audit of internal controls.
UpGuard scans Veridian Solutions daily across 52 external risk signals. Get notified the moment something changes: a new vulnerability, a breach, or a posture shift.
The evidence behind the rating. 52 checks across 8 categories, 14 currently failing. Failed checks are listed first.
When secure cookies are not used, there is an increased risk of third parties intercepting information contained in these cookies. The website configuration should be changed so that all 'Set-Cookie' headers include 'secure'.
No valid Content Security Policy is implemented. This increases the risk of XSS and clickjacking attacks.
When HttpOnly cookies are not used, the cookies can be accessed on the client, which enables certain type of client-side attacks. The website configuration should be changed to enforce HttpOnly cookies.
Browsers may interpret files as a different MIME type than what is specified in the Content-Type HTTP header. This can lead to MIME confusion attacks.
Ensuring the server information header is not exposed reduces the ability of attackers to exploit certain vulnerabilities.
Information about specific technology used on the server is obscured.
Browsers are prevented from displaying this website's content in frames. This helps mitigate clickjacking attacks.
The website's Referrer Policy is not configured to allow unsafe information to be sent in the referrer header.
Ensuring the ASP.NET version header is not exposing a specific version makes it harder for attackers to exploit certain vulnerabilities.
Ensuring the ASP.NET version header is not exposed makes it harder for attackers to exploit certain vulnerabilities.
The page appears to be maintained.
DMARC policy is p=none. This provides no protection against fraudulent emails. The DMARC policy should be migrated to p=quarantine, and eventually p=reject.
DMARC protects against fraudulent emails being sent from a domain.
Sender Policy Framework (SPF) records prevent spammers from sending messages with forged addresses.
Sender Policy Framework (SPF) record strictly enforces specific domains allowed to send email on its behalf.
Sender Policy Framework (SPF) record passes basic syntax checks.
Sender Policy Framework (SPF) record does not include the ptr mechanism.
The 'HTTP' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.
The 'HTTPS' service is running and exposed to the internet. The configuration of the server should be reviewed and unnecessary ports closed.
DNSSEC records prevent third parties from forging the records that guarantee a domain's identity. DNSSEC should be configured for this domain.
The domain does not contain a valid Certification Authority Authorization (CAA) record. A CAA record indicates which Certificate Authorities (CAs) are authorized to issue certificates for a domain.
No unregistered MX records that could lead to receiving mail on behalf of the target organization were detected.
No dangling DNS records that could lead to subdomain takeover were detected.
SSL is the standard encryption method for browsing websites. Enabling SSL requires installing an SSL certificate on the site.
The domain is still accessible over HTTP. All HTTP requests should be redirected to HTTPS.
The site's hostname does not match the SSL certificate. The domain name should be added to the certificate, either as a Subject Alternative Name or as the Common Name.
Without HSTS enforced, people browsing this site are more susceptible to man-in-the-middle attacks. The server should be configured to support HSTS.
Weak cipher suites can potentially be broken by a well resourced attacker, and should not be supported by the server unless very old devices or browsers must be supported.
The site's certificate chain was checked against our list of revoked certificates.
SSL certificate has not expired.
No insecure SSL/TLS versions are available for this site.
The SSL certificate presented by the server has an expiration period shorter than 398 days.
SSL certificate does not expire in less than 20% of its total valid period.
Industry standard SHA-256 encryption in use.
The site's public certificate provides at least 112 bits of security strength.
Our scans have not found any evidence of infostealer malware infections associated with this organisation's domain.
No cloud storage service configured to allow anonymous file listing was detected.
The domain index is not a listable directory.
This IP/domain has not been reported as a source of botnet activity in the last 30 days.
This IP/domain did not appear on any list of IPs and domains known to perform brute force login attempts in the last 30 days.
This IP/domain has been reported for distributing malware in the last 30 days.
This IP/domain has not been reported for performing unsolicited scanning in the last 30 days.
This IP/domain has not been reported as a phishing site in the last 30 days.
This IP/domain has not been reported as a source of botnet activity in the last 90 days.
This IP/domain did not appear on any list of IPs and domains known to perform brute force login attempts in the last 90 days.
This IP/domain has been reported for distributing malware in the last 90 days.
This IP/domain has not been reported for performing unsolicited scanning in the last 90 days.
This IP/domain has not been reported as a phishing site in the last 90 days.
A bug in OpenSSL's implementation of the TLS heartbeat extension allows access to portions of memory on the targeted host e.g. cryptographic keys and passwords.
The server does not support SSLv3, and is not vulnerable to the POODLE attack.
The server does not offer RSA_EXPORT cipher suites, so clients are not vulnerable to the FREAK attack.
The server is using strong Diffie-Hellman parameters and is not vulnerable to the Logjam attack.
UpGuard scans Veridian Solutions daily across 52 external risk signals. Get notified the moment something changes: a new vulnerability, a breach, or a posture shift.