Spectra Assure
Community
passEverything is awesome!
Scanned: 5 days ago

cAzureStorage

latest
Top 10k
Sample Azure Storage DSC resource that copies files from Azure storage account using a key
License: unknown
Published: over 9 years ago




SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Popularity

13.07k
Total Downloads
Contributors
Declared Dependencies
0
Dependents

Top issues

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. Some open source repositories allow the developers to take down software component versions that they have published. For open source projects, version unpublishing is uncommon. Versions are typically removed due to a security incident, such as malicious code tampering or accidental development secrets exposure. Software developers often prioritize taking down such packages before informing the community that they have experienced a security incident. Therefore, it is prudent to review the reasons behind software version removals as these events might be a signal of an ongoing software supply chain attack.

Prevalence in PowerShell Gallery community

No prevalence information at this time

Next steps

Review software component documentation for the reasons behind the recent version removal.
If the software version was removed due to a security incident, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
Avoid using this software package until it is vetted as safe.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community. it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of using components that are rarely used to build applications lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in PowerShell Gallery community

1 packages
found in
Top 100
4 packages
found in
Top 1k
5 packages
found in
Top 10k
20 packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Problem

Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures verify the origin and the integrity of the object they apply to. The integrity validation relies on the cryptographic strength of the encryption and the hash verification algorithm. If either of the two is considered weak by current standards, there is a chance the signed object could be maliciously modified, without triggering the integrity failure check.

Prevalence in PowerShell Gallery community

87 packages
found in
Top 100
354 packages
found in
Top 1k
1060 packages
found in
Top 10k
1.69k packages
in community

Next steps

Create signatures with strong ECC key-length of at least 224 bits, or RSA key-length of at least 2048 bits, and use SHA256 as the hashing algorithm. While encryption key-length upgrade does require you to obtain a new certificate, the hashing algorithm can freely be selected during signing.
With Microsoft SignTool, you can specify the hashing algorithm using the /fd SHA256 parameter.

Top behaviors

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
91 packages
found in
Top 100
509 packages
found in
Top 1k
3132 packages
found in
Top 10k
5.29k packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
100 packages
found in
Top 100
804 packages
found in
Top 1k
6511 packages
found in
Top 10k
11.95k packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
81 packages
found in
Top 100
308 packages
found in
Top 1k
1886 packages
found in
Top 10k
3.02k packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
6 packages
found in
Top 100
80 packages
found in
Top 1k
685 packages
found in
Top 10k
1.05k packages
in community

Prevalence in PowerShell Gallery community

Behavior often found in this community (Common)
76 packages
found in
Top 100
404 packages
found in
Top 1k
2152 packages
found in
Top 10k
3.59k packages
in community

Top vulnerabilities

No vulnerabilities found.