Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

[January 2023] eRegs parsing requirements #735

Closed
1 of 4 tasks
Tracked by #137
pkfec opened this issue Dec 29, 2022 · 2 comments
Closed
1 of 4 tasks
Tracked by #137

[January 2023] eRegs parsing requirements #735

pkfec opened this issue Dec 29, 2022 · 2 comments
Assignees
Labels
Security: general General security concern or issue
Milestone

Comments

@pkfec
Copy link
Contributor

pkfec commented Dec 29, 2022

Take a look at Snyk vulnerabilities for requirements-parsing.txt and upgrade relevant packages to maintain the parsing tool

Reference ticket: #730

Action Items :

  • Check and document parsing requirements and upgrades in Snyk
    • Run: snyk test --file=requirements-parsing.txt --package-manager=pip

Completion criteria:

  • Upgrade vulnerable packages in requirements-parsing.txt
  • Setup and parse 2022 regulations on local environment
  • Create a new ticket to check for the month of February 2023
@pkfec pkfec added Pipeline: PI Backlog Security: general General security concern or issue labels Dec 29, 2022
@pkfec pkfec added this to the Sprint 20.4 milestone Jan 11, 2023
@pkfec pkfec self-assigned this Jan 17, 2023
@pkfec
Copy link
Contributor Author

pkfec commented Jan 19, 2023

Remediation not available for cryptography as of 01/19/2023.
More on cryptography: pyca/cryptography#7940

@pkfec
Copy link
Contributor Author

pkfec commented Jan 25, 2023

cryptography pkg cannot be updated at this time as there is no remediation or fix available. Will check again in Feb ticket

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Security: general General security concern or issue
Projects
None yet
Development

No branches or pull requests

1 participant