Difference between revisions of "Black Duck Software Composition Analysis"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
* [[Black Duck]] (Black Duck Hub and Protecode SC) | * [[Black Duck]] (Black Duck Hub and Protecode SC) | ||
* [[Black Duck Binary Analysis]] | * [[Black Duck Binary Analysis]] | ||
| − | + | * [[Black Duck Protex]] | |
== Editions == | == Editions == | ||
Revision as of 14:31, 9 February 2020
- Black Duck (Black Duck Hub and Protecode SC)
- Black Duck Binary Analysis
- Black Duck Protex
Editions
See also
- Software Composition Analysis (SCA): Flexera, FOSSA, GitLab Ultimate, JFrog Xray, Snyk, Sonatype, Synopsys: Black Duck, Veracode, WhiteHat Security, WhiteSource, Bill of Materials (BOM), Semgrep, Clair
- BOM
- Security: Security portfolio, Security standards, Hardening, CVE, CWE, Wireless Network Hacking, vulnerability scanner, Security risk assessment, SCA, Application Security Testing, OWASP, Data leak, NIST, SANS, MITRE, Security policy, Access Control attacks, password policy, password cracking, Password manager, MFA, OTP, UTF, Firewall, DoS, Software bugs, MITM, Certified Ethical Hacker (CEH) Contents, Security+ Malware, FIPS, DLP, Network Access Control (NAC), VAPT, SIEM, EDR, SOC, pentest, PTaaS, Clickjacking, MobSF, Janus vulnerability, Back Orifice, Backdoor, CSO, CSPM, PoLP, forensic, encryption, Keylogger, Pwn2Own, CISO, Prototype pollution
Advertising:
