8 posts with this tag.
Every vulnerability scanner produces output that security practitioners can read and most clients cannot. A scan of a mid-size client environment returns hundreds of findings, organized by plugin ID, …
Read more →Running vulnerability assessments for a single organization is a contained problem. You import a scan, triage the findings, generate a report, and deliver it. The data belongs to one client. The …
Read more →Some vulnerabilities are practically furniture. SSL weak cipher suites. Missing security headers. Insufficient account lockout policies. SMBv1 still enabled on a file server. If you have been doing …
Read more →Running a Nessus scan is the easy part. What happens next is where most teams lose time. The scan produces a list of findings. Someone has to decide which ones are real, which are noise, which need to …
Read more →Nessus is excellent at scanning. What it produces when it is finished is not a report. It is a list of findings, organized by plugin and severity, with remediation guidance attached. That output is …
Read more →Twenty-five years is an eternity in cybersecurity. Products get acquired, deprecated, replaced by the next generation of something, or simply abandoned while the industry moves on. Nessus has been in …
Read more →The vulnerability management industry has a pricing problem. If you run a three-person security team, a solo consultancy, or an IT department where “security team” is a generous …
Read more →Most ticketing systems accept email. This single fact makes the entire API integration question considerably less important than it first appears. The common assumption when trying to route Nessus …
Read more →