KYND SIGNALS
Everything about KYND's Signals reports
Vulnerabilities
- Essential and Advisable actions
- Remote Desktop Protocol (RDP)
- Remote Procedure Call (RPC)
- Samba or Server Message Block (SMB)
- Virtual Network Computing (VNC)
- Windows PowerShell
- Out-of-date or vulnerable developer access services
- TeamViewer
- End of Life Microsoft software
- Obsolete Software
- Database vulnerabilities
- Unsafe email sender protection (SPF)
- Email spoofing policy (DMARC)
- Potentially vulnerable services
Frequently Asked Questions
- How did you perform a scan if I didn't give you a list of IPs?
- The vulnerabilities you found are managed by a third party and not within my control.
- An email from our organisation is connecting an unrelated domain into our results
- KYND has discovered a vulnerability that is registered under a former employee/IT provider name, or is no longer in use.
- KYND has flagged a load balancing port as a vulnerability
- I have a WAF in place. Is that an acceptable reason for ports to be open?
- I have MFA enabled. Is that an acceptable resolution to the vulnerabilities highlighted in the report?
- A vulnerability in the report is behind a VPN. Does this resolve the issue?
- KYND has identified a vulnerability located in a DMZ. Is that secure?
- An open RDP port that's been found in the KYND report is being actively monitored. Is that secure?
- Why has KYND flagged a developer access port as a risk?
- I have patched the services on my developer access port, why is KYND still flagging it as out of date?
- The vulnerability discovered by KYND is always disabled, so is it a risk?
- The ports identified by KYND are filtered. Are they still a risk?
- My honeypot port has been flagged by KYND.
- I can't close or hide the port identified in my SIGNALS report. What should I do?
- Why does KYND flag End of Life Microsoft services?
- My report has flagged an exposed database. What do you mean?