Difference between revisions of "Software Composition Analysis (SCA)"
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
* [[Binary repository manager]] | * [[Binary repository manager]] | ||
* {{SCA}} | * {{SCA}} | ||
| + | * {{security}} | ||
[[Category:Security]] | [[Category:Security]] | ||
Revision as of 10:08, 9 February 2020
This article is a Draft. Help us to complete it.
- Flexera
- FOSSA
- GitLab
- JFrog Xray
- Snyk
- Sonatype
- Synopsys
- Veracode
- WhiteHat Security
- WhiteSource (2016)
See also
- CA Technologies
- Forrester, Gartner
- Binary repository manager
- 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
- 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:
