shieldworks aegis issues

shieldworks / aegis

Aegis: Keep Your Secrets… Secret

https://vsecm.com

MIT License

31 stars 3 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

The project MUST use at least one static analysis tool with rules or approaches to look for common vulnerabilities in the analyzed language or environment, if there is at least one FLOSS tool that can implement this criterion in the selected language. [

#439 v0lkan opened 1 year ago
0
The project MUST provide an assurance case that justifies why its security requirements are met. The assurance case MUST include: a description of the threat model, clear identification of trust boundaries, an argument that secure design principles have been applied, and an argument that common implementation security weaknesses have been countered.

#438 v0lkan opened 1 year ago
0
Hardening mechanisms SHOULD be used in the software produced by the project so that software defects are less likely to result in security vulnerabilities.

#437 v0lkan opened 1 year ago
0
The project results MUST check all inputs from potentially untrusted sources to ensure they are valid (an *allowlist*), and reject invalid inputs, if there are any restrictions on the data at all.

#436 v0lkan opened 1 year ago
0
It is SUGGESTED that in the version control system, each important version tag (a tag that is part of a major release, minor release, or fixes publicly noted vulnerabilities) be cryptographically signed and verifiable as described in signed_releases.

#435 v0lkan opened 1 year ago
0
The project MUST cryptographically sign releases of the project results intended for widespread use, and there MUST be a documented process explaining to users how they can obtain the public signing keys and verify the signature(s). The private key for these signature(s) MUST NOT be on site(s) used to directly distribute the software to the public

#434 v0lkan opened 1 year ago
0
The software produced by the project SHOULD support secure protocols for all of its network communications, such as SSHv2 or later, TLS1.2 or later (HTTPS), IPsec, SFTP, and SNMPv3. Insecure protocols such as FTP, HTTP, telnet, SSLv3 or earlier, and SSHv1 SHOULD be disabled by default, and only enabled if the user specifically configures it.

#433 v0lkan opened 1 year ago
0
The project MUST support storing authentication credentials (such as passwords and dynamic tokens) and private cryptographic keys in files that are separate from other information (such as configuration files, databases, and logs), and permit users to update and replace them without code recompilation.

#432 v0lkan opened 1 year ago
0
The project SHOULD support multiple cryptographic algorithms, so users can quickly switch if one is broken. Common symmetric key algorithms include AES, Twofish, and Serpent. Common cryptographic hash algorithm alternatives include SHA-2 (including SHA-224, SHA-256, SHA-384 AND SHA-512) and SHA-3.

#431 v0lkan opened 1 year ago
0
The project MUST implement secure design principles (from "know_secure_design"), where applicable.

#430 v0lkan opened 1 year ago
0
Projects MUST be maximally strict with warnings in the software produced by the project, where practical

#429 v0lkan opened 1 year ago
0
The project MUST include, in its documented instructions for change proposals, the policy that tests are to be added for major new functionality.

#428 v0lkan opened 1 year ago
0
The project MUST have a formal written policy that as major new functionality is added, tests for the new functionality MUST be added to an automated test suite.

#427 v0lkan opened 1 year ago
0
The project MUST have FLOSS automated test suite(s) that provide at least 80% statement coverage if there is at least one FLOSS tool that can measure this criterion in the selected language.

#426 v0lkan opened 1 year ago
0
The project MUST add regression tests to an automated test suite for at least 50% of the bugs fixed within the last six months.

#425 v0lkan opened 1 year ago
0
An automated test suite MUST be applied on each check-in to a shared repository for at least one branch. This test suite MUST produce a report on test success or failure.

#424 v0lkan opened 1 year ago
0
The project SHOULD avoid using deprecated or obsolete functions and APIs where FLOSS alternatives are available in the set of technology it uses (its "technology stack") and to a supermajority of the users the project supports (so that users have ready access to the alternative)

#423 v0lkan opened 1 year ago
0
The project MUST either: make it easy to identify and update reused externally-maintained components; or use the standard components provided by the system or programming language. Then, if a vulnerability is found in a reused component, it will be easy to update that component.

#422 v0lkan opened 1 year ago
0
Projects MUST monitor or periodically check their external dependencies (including convenience copies) to detect known vulnerabilities, and fix exploitable vulnerabilities or verify them as unexploitable.

#421 v0lkan opened 1 year ago
0
The project MUST list external dependencies in a computer-processable way.

#420 v0lkan opened 1 year ago
0
The project MUST provide a way for potential developers to quickly install all the project results and support environment necessary to make changes, including the tests and test environment. This MUST be performed with a commonly-used convention.

#419 v0lkan opened 1 year ago
0
The project MUST provide a way to easily install and uninstall the software produced by the project using a commonly-used convention.

#418 v0lkan opened 1 year ago
0
The project MUST be able to repeat the process of generating information from source files and get exactly the same bit-for-bit result.

#417 v0lkan opened 1 year ago
0
The build system for the software produced by the project MUST NOT recursively build subdirectories if there are cross-dependencies in the subdirectories

#416 v0lkan opened 1 year ago
0
The project MUST automatically enforce its selected coding style(s) if there is at least one FLOSS tool that can do so in the selected language(s)

#415 v0lkan opened 1 year ago
0
The project MUST identify the specific coding style guides for the primary languages it uses, and require that contributions generally comply with it.

#414 v0lkan opened 1 year ago
0
The project MUST have a documented process for responding to vulnerability reports.

#413 v0lkan opened 1 year ago
0
The project MUST give credit to the reporter(s) of all vulnerability reports resolved in the last 12 months, except for the reporter(s) who request anonymity. If there have been no vulnerabilities resolved in the last 12 months, select "not applicable"

#412 v0lkan opened 1 year ago
0
The project MUST maintain the most often used older versions of the product or provide an upgrade path to newer versions. If the upgrade path is difficult, the project MUST document how to perform the upgrade (e.g., the interfaces that have changed and detailed suggested steps to help upgrade). [

#411 v0lkan opened 1 year ago
0
The software produced by the project SHOULD be internationalized to enable easy localization for the target audience's culture, region, or language. If internationalization (i18n) does not apply (e.g., the software doesn't generate text intended for end-users and doesn't sort human-readable text), select "not applicable"

#410 v0lkan opened 1 year ago
0
The project (both project sites and project results) SHOULD follow accessibility best practices so that persons with disabilities can still participate in the project and use the project results where it is reasonable to do so.

#409 v0lkan opened 1 year ago
0
The project repository front page and/or website MUST identify and hyperlink to any achievements, including this best practices badge, within 48 hours of public recognition that the achievement has been attained.

#408 v0lkan opened 1 year ago
0
The project MUST make an effort to keep the documentation consistent with the current version of the project results (including software produced by the project). Any known documentation defects making it inconsistent MUST be fixed. If the documentation is generally current, but erroneously includes some older information that is no longer true, just treat that as a defect, then track and fix as usual.

#407 v0lkan opened 1 year ago
0
The project MUST provide a "quick start" guide for new users to help them quickly do something with the software. (URL required)

#406 v0lkan opened 1 year ago
0
The project MUST document what the user can and cannot expect in terms of security from the software produced by the project (its "security requirements").

#405 v0lkan opened 1 year ago
0
The project MUST include documentation of the architecture (aka high-level design) of the software produced by the project.

#404 v0lkan opened 1 year ago
0
The project MUST have a documented roadmap that describes what the project intends to do and not do for at least the next year.

#403 v0lkan opened 1 year ago
0
The project MUST be able to continue with minimal interruption if any one person dies, is incapacitated, or is otherwise unable or unwilling to continue support of the project. In particular, the project MUST be able to create and close issues, accept proposed changes, and release versions of software, within a week of confirmation of the loss of support from any one individual. This MAY be done by ensuring someone else has any necessary keys, passwords, and legal rights to continue the project. Individuals who run a FLOSS project MAY do this by providing keys in a lockbox and a will providing any needed legal rights

#402 v0lkan opened 1 year ago
0
The project MUST clearly define and publicly document the key roles in the project and their responsibilities, including any tasks those roles must perform. It MUST be clear who has which role(s), though this might not be documented in the same way.

#401 v0lkan opened 1 year ago
0
The project MUST adopt a code of conduct and post it in a standard location.

#400 v0lkan opened 1 year ago
0
The project MUST clearly define and document its project governance model (the way it makes decisions, including key roles).

#399 v0lkan opened 1 year ago
0
The project SHOULD have a legal mechanism where all developers of non-trivial amounts of project software assert that they are legally authorized to make these contributions. The most common and easily-implemented approach for doing this is by using a Developer Certificate of Origin (DCO), where users add "signed-off-by" in their commits and the project links to the DCO website. However, this MAY be implemented as a Contributor License Agreement (CLA), or other legal mechanism.

#398 v0lkan opened 1 year ago
0
The information on how to contribute MUST include the requirements for acceptable contributions (e.g., a reference to any required coding standard).

#397 v0lkan opened 1 year ago
0
The project SHOULD include many run-time assertions in the software it produces and check those assertions during dynamic analysis.

#396 v0lkan opened 1 year ago
0
The project MUST apply at least one dynamic analysis tool to any proposed major production release of the software produced by the project before its release. [

#395 v0lkan opened 1 year ago
0
Hardening mechanisms MUST be used in the software produced by the project so that software defects are less likely to result in security vulnerabilities.

#394 v0lkan opened 1 year ago
0
The project MUST have performed a security review within the last 5 years. This review MUST consider the security requirements and security boundary.

#393 v0lkan opened 1 year ago
0
The project website, repository (if accessible via the web), and download site (if separate) MUST include key hardening headers with nonpermissive values.

#392 v0lkan opened 1 year ago
0
The software produced by the project MUST, if it supports or uses TLS, support at least TLS version 1.2. Note that the predecessor of TLS was called SSL. If the software does not use TLS, select "not applicable" (

#391 v0lkan opened 1 year ago
0
The software produced by the project MUST support secure protocols for all of its network communications, such as SSHv2 or later, TLS1.2 or later (HTTPS), IPsec, SFTP, and SNMPv3. Insecure protocols such as FTP, HTTP, telnet, SSLv3 or earlier, and SSHv1 MUST be disabled by default, and only enabled if the user specifically configures it. If the software produced by the project does not support network communications, select "not applicable"

#390 v0lkan opened 1 year ago
0

Previous Next