← Back to rule catalog
Rule R-INSTALLED-PACKAGE-CRYPTO
active

Managed packages are supply-chain PQC exposures

Advisory rule for opaque third-party packages that may contain unmanaged cryptography.

Applies to
installed-package
Cases
1
Evaluation order
100
Tags
packages, supply-chain, advisory
Overlay-specific scope
nis2, dora, swift-csp
Engine description
Installed managed packages should be tracked as PQC supply-chain exposures.

Match cases

Case 1 low · advisory
When
  • kind equals installed-package
Finding title template
{{asset.name}} — supply-chain PQC exposure
Current crypto template
Third-party managed package; cryptographic internals not inspectable
Severity / status
low · advisory
Effort / deadline
medium
Recommended replacement
Request the vendor's cryptographic inventory and PQC migration statement. Track the package as a supply-chain exposure until the vendor publishes a roadmap for any RSA, ECC, or proprietary crypto that aligns with FIPS 203 and FIPS 204.
Rationale
Managed packages are opaque to QuantumShield scanning. NIST SP 800-53 supply-chain controls and NIST IR 8547 both require transition planning for dependent products and services whose cryptography is outside direct code review.
Citations
  • NIST_SP_800_53 · Security and Privacy Controls for Information Systems and Organizations
  • ENISA_PQC_2024 · Post-Quantum Cryptography: Integration study
  • NIST_IR_8547 · Transition to Post-Quantum Cryptography Standards

Opaque dependencies should be reviewed as policy, not hidden behind a hard-coded special case.