Think about you are contemplating a brand new automotive for your loved ones. Earlier than making a purchase order, you consider its security scores, gas effectivity, and reliability. You would possibly even take it for a take a look at drive to make sure it meets your wants. The identical strategy ought to be utilized to software program and {hardware} merchandise earlier than integrating them into a company’s surroundings. Simply as you would not purchase a automotive with out realizing its security options, you should not deploy software program with out understanding the dangers it introduces.
The Rising Menace of Provide Chain Assaults
Cybercriminals have acknowledged that as a substitute of attacking a company head-on, they’ll infiltrate by the software program provide chain—like slipping counterfeit elements into an meeting line. In response to the 2024 Sonatype State of the Software program Provide Chain report, attackers are infiltrating open-source ecosystems at an alarming price, with over 512,847 malicious packages detected final 12 months alone—a 156% improve from the earlier 12 months. Conventional safety instruments and processes typically miss these threats, leaving organizations unprepared.
One main instance in 2024 was a year-long provide chain assault uncovered within the Python Package deal Index (PyPI). Attackers uploaded malicious packages disguised as official AI chatbot instruments, hoping to trick builders into integrating them into their tasks. These packages contained dangerous code designed to steal delicate information and execute distant instructions on contaminated techniques. As a result of PyPI is extensively used throughout varied industries, this assault had the potential to compromise hundreds of functions earlier than safety researchers at Kaspersky detected and reported the malicious exercise. This incident highlights how attackers are more and more exploiting trusted repositories to distribute malware, reinforcing the necessity for extra in-depth measures when evaluating software program.
A Fingers-On Method to Danger Evaluation: Product Safety Testing
Organizations want a structured and repeatable approach to consider software program and {hardware} dangers earlier than introducing them into their environments. This course of, generally known as Product Safety Testing (PST), is about answering key questions:
- What dangers does this product introduce to my community?
- Ought to we use this product, or is there a safer different?
- If we use it, what mitigations ought to be put in place to attenuate danger?
PST is not nearly scanning for vulnerabilities—it is about understanding how a product behaves in your particular surroundings and figuring out its general danger affect. Given the huge variety of third-party elements utilized in fashionable IT, it is unrealistic to scrutinize each software program package deal equally. As a substitute, safety groups ought to prioritize their efforts primarily based on enterprise affect and assault floor publicity. Excessive-privilege functions that ceaselessly talk with exterior companies ought to bear product safety testing, whereas lower-risk functions might be assessed by automated or much less resource-intensive strategies. Whether or not achieved earlier than deployment or as a retrospective evaluation, a structured strategy to PST ensures that organizations give attention to securing probably the most essential property first whereas sustaining general system integrity.
Studying to Suppose Pink, Act Blue
The SANS SEC568 course is designed to construct sensible expertise in PST. It focuses on black-box testing, a technique that simulates real-world circumstances the place the supply code is not out there. This makes it extremely relevant for evaluating third-party merchandise that organizations haven’t got direct management over. The course follows the precept of Suppose Pink, Act Blue—by studying offensive techniques, organizations can higher defend in opposition to them.
Whereas Product Safety Testing won’t ever forestall a breach of a 3rd social gathering out of your management, it’s needed to permit organizations to make knowledgeable selections about their defensive posture and response technique. Many organizations observe a regular technique of figuring out a necessity, deciding on a product, and deploying it and not using a deep safety analysis. This lack of scrutiny can go away them scrambling to find out the affect when a provide chain assault happens.
By incorporating PST into the decision-making course of, safety groups achieve essential documentation, together with dependency mapping, menace fashions, and particular mitigations tailor-made to the expertise in use. This proactive strategy reduces uncertainty, permitting for quicker and simpler responses when vulnerabilities emerge. Somewhat than relying solely on broad business mitigations, organizations with PST documentation can implement focused safety controls that reduce danger earlier than a breach even occurs.
Who leverages Product Safety Testing?
No matter job title, having a powerful basis in product safety testing results in higher safety posture and preparedness throughout the total group. Whereas the apparent match is product safety testing groups can leverage these methodologies to guage third-party software program in addition to their very own in-house merchandise – product safety testing is not restricted to at least one particular position. It is a invaluable ability set that enhances varied positions inside a company. Safety auditors can use PST to tailor evaluations to a company’s distinctive dangers and compliance wants, whereas penetration testers can transcend easy vulnerability scans to investigate unknown protocols and proprietary software program. Software builders profit by understanding how attackers exploit safety flaws, serving to them write safer code from the beginning, whereas SOC analysts can use these expertise to detect and mitigate threats launched by new software program and {hardware}. Even decision-makers achieve insights from PST, because it helps them make knowledgeable selections about danger, safety investments, and mitigation methods. It is necessary to keep in mind that it is inconceivable to detect, mitigate, exploit, or develop what we do not perceive.
To achieve hands-on expertise in product safety testing, take into account attending SEC568 in Orlando from April 13-18, 2024. This coaching will present the technical basis wanted to evaluate software program and {hardware} safety successfully. Similar to taking a automotive for a take a look at drive earlier than buying, making use of a structured strategy to product safety testing permits organizations to totally perceive potential dangers earlier than deployment. By following a repeatable methodology, safety groups can scale back dangers and be higher ready for future threats.
Be aware: This text was expertly written and contributed by Douglas McKee, the Govt Director of Menace Analysis at SonicWall, in addition to the lead creator and teacher for SANS SEC568.