The Frontline of Attack
Securing Your Python, Perl and Tcl Supply Chains
Webinar: Wednesday, Aug. 18, 2021 | 10am PT / 1pm ET | 45 min. plus Q&A
In response, the US government has issued an Executive Order calling for the adoption of software security best practices. Subsequently, Google has introduced a framework for ensuring software supply chain integrity (SLSA).
Are your applications secure from open source supply chain attacks?
Join our webinar to learn more about the Executive Order and SLSA, and how you can secure your Python, Perl and Tcl supply chains with the ActiveState Platform, including:
- Software Bill of Materials (SBOM): Produce a list of all components and dependencies for your compliance team.
- Vulnerability Remediation: Automatically identify vulnerabilities from the start of development and remediate them in minutes.
- Provenance: Establish the origin of software components by building all packages from source code, imported from their official
- Supply Chain Integrity: Understand how you can meet the four levels of Google’s SLSA standards.
Before you attend, take our survey to assess the maturity of your open source supply chain security. Be one of the first 10 people to complete the survey and join the webinar to get a $50 Amazon gift card!
Director of Product Management, ActiveState
Related Resources
President Biden: Secure Your Software Supply Chain
The US Executive Order has implications for not only software and FedRAMP vendors, but the private sector at large. Learn more about its requirements, such as implementing open source provenance, vulnerability remediation and having a Software Bill of Materials.
3 Ways the Activestate Platform Can Secure Your Open Source Supply Chain
In recent cyberattacks, bad actors have compromised the upstream development environment of software vendors. Learn how you can secure your open source supply chain from import through consumption via provenance, verifiably reproducible builds and code signing.
Take Our Survey: Open Source Supply Chain Security
Assess your open source supply chain security, including how you import open source code, your build process, and how you know if the open source code you’re running is secure.