Your glossary for risk and compliance
Helpful definitions of all of the terms you need to know to better manage risk and compliance.
TermsAFSL Authorised Representative AICPA Annex A Controls ASIC Attestation of Compliance (AOC) Business Continuity Management Communication and consultation Compliance Automation Software Compliance Risk Management Consequence Context control Cybersecurity Cybersecurity Maturity Model Certification (CMMC) FedRAMP Governance Risk & Compliance (GRC) GPDR HIPAA HITRUST How many controls are there in ISO 27001? Incident Management Information Security Management System (ISMS) ISMS Governing Body ISO 27001 ISO 27001 certified ISO/IEC 27000 ISO/IEC 27004 ISO/IEC 27005 ISO/IEC 27017 ISO/IEC 27018 Level of risk Likelihood Notifiable Data Breach OAIC Policy Management Risk Risk analysis Risk identification Risk management Risk management framework Risk management plan Risk management policy Risk management process Risk owner Risk profile Risk review Risk source Risk treatment SOC 1 SOC 2 SOC 3 SOC Reports SOC Trust Services Criteria (TSC) SSAE 16 SSAE 18 Stakeholder Third Party Risk Management Vendor Assessment Vendor Management Policy Vendor Review Vulnerability Vulnerability Management What are the ISO 27001 controls? What is an ISO 27001 internal audit? What is an ISO 27001 risk treatment plan? What is an IT security policy? What is Hacking? What is ISO 27002? What is PaaS (Platform-as-a-Service)? What is the ASD Essential 8? What is the ISO 27001 management review? What is the ISO 27001 Stage 1 Audit? What is the ISO 27001 stage 2 audit?
What is a Vulnerability?
Mistakes happen, even in the process of building and coding technology. What’s left behind from these mistakes is commonly referred to as a bug. While bugs aren’t inherently harmful (except to the potential performance of the technology), many can be taken advantage of by nefarious actors—these are known as vulnerabilities. Vulnerabilities can be leveraged to force software to act in ways it’s not intended to, such as gleaning information about the current security defenses in place.
Once a bug is determined to be a vulnerability, it is registered by MITRE as a CVE, or common vulnerability or exposure, and assigned a Common Vulnerability Scoring System (CVSS) score to reflect the potential risk it could introduce to your organization. This central listing of CVEs serves as a reference point for vulnerability scanners.
Generally speaking, a vulnerability scanner will scan and compare your environment against a vulnerability database, or a list of known vulnerabilities; the more information the scanner has, the more accurate its performance. Once a team has a report of the vulnerabilities, developers can use penetration testing as a means to see where the weaknesses are, so the problem can be fixed and future mistakes can be avoided. When employing frequent and consistent scanning, you'll start to see common threads between the vulnerabilities for a better understanding of the full system.
Back to glossary search