The holiday season is upon us. Thanksgiving, in the United States, is around the corner where thousands of pounds of turkey will be eaten. Then we will weather the chaos Black Friday sales. But for merchants it's time to think about a week from now - Cyber Monday (the Monday after Black Friday). In the past, we have recommended cybersecurity best practices for purchasing goods online, and many other vendors will cover how to securely use credit cards and touchless payment systems to protect your identity and purchases.
This year however, we want to focus on merchants. Consumers will always be a target for theft during the holiday season, but how are merchants themselves being compromised, and how can they protect themselves against the latest threats?
Let us start with basic cybersecurity hygiene and discuss the vulnerability management lifecycle. See the graphic below.
Design
The beginning of every vulnerability management lifecycle starts with the design. Whether this is a custom application, purchased program, or even DevOps with automation; the design or purchase should take into consideration basic security hygiene. This includes security basics regarding coding, storage of sensitive information, to the crown jewels of the enterprise and merchants. If security questions are not asked up front, the implementation of any solution could pose an unacceptable risk to the business and lead to a breach of client data.
Development
The development, proof of concept, and deployment of any new technology should be tested, code reviewed (if applicable) and assessed for risks before product implementation. This not only includes vulnerability assessments but also configuration hardening and placement in secure zones within the environment. It is one thing to accept the risks of a known application, but entirely another to place it on a high-risk network or directly on the Internet. Development, and accompanying deployment, begin the cyclical portion of a vulnerability management lifecycle.
Assessment
As resources are placed in production, periodic vulnerability assessments are required. An assessment is the act of actually looking for risks through any vehicle like a network scanner or patch management solution. Vulnerability management is the lifecycle of an assessment including remediation (mitigation) and re-measurement. For merchants, if these are not done on a routine basis, gaps in security will form and be targeted by threat actors.
Measure
The vulnerability management lifecycle requires periodic and frequent measurements to determine if new vulnerabilities are present, and if mitigation and remediation strategies are effective. Typically, measurements are performed using service level agreements to age a vulnerability:
- Date of public disclosure
- Date of Audit Release in an Assessment solution
- Discovery date of vulnerability
- Date of mitigation or remediation
- SLA measurement for date of discovery to closure
- Age of outstanding risks critical to the business
- Number of acceptable Exclusions or deviations
- Remediation – the actual application of a security patch (update) to fix a vulnerability
- Mitigation – the removal of software, changing of a configuration, or the intentional modification of a resource to block the vulnerability (local HIPS for example) and potentially its corresponding exploit (if available)
- Exclusion – the acceptance of the vulnerabilities risk (also called a deviation) due to remediation or mitigation strategies that will impact the business
