Should

{
  "id": "MLC-T-CYB-003936",
  "term": "Should",
  "field": "Cybersecurity",
  "definition": "1. The term used to indicate an important recommendation. Ignoring the recommendation could result in undesirable results. Note that should may be coupled with not to become should not.\n\n2. Used to indicate a strong recommendation but not a requirement of this standard. Ignoring the recommendation could result in undesirable results.\n\n3. Used to indicate a strong recommendation but not a requirement of this standard. Ignoring the recommendation could lead to undesirable results.\n\n4. Term used to indicate a strong recommendation but not a requirement of this standard. Ignoring the recommendation could result in undesirable results.\n\n5. Used to indicate a strong recommendation but not a requirement of this document. Ignoring the recommendation could lead to undesirable results.\n\n6. This term is used to indicate an important recommendation. Ignoring the recommendation could result in undesirable results. Note that should may be coupled with not to become should not.\n\n7. Is recommended to.\n\n8. An important recommendation. Ignoring the recommendation could result in undesirable results. Note that should may be coupled with not to become should not.\n\n9. This term is used to indicate a very important recommendation. Ignoring the recommendation could result in undesirable results. Note that should may be coupled with not to become should not.\n\n10. Used to indicate a strong recommendation, but not a requirement of this Recommendation.\n\n11. Used to indicate a highly desirable feature for a DRBG mechanism that is not necessarily required by this Recommendation. \"Should\" may be coupled with \"not\" to become \"should not.\"\n\n12. When shown in a bold font, this term is used to indicate an important recommendation. Ignoring the recommendation could result in undesirable results. Note that should may be coupled with not to become should not.\n\n13. This term is used to indicate an important recommendation. Ignoring the recommendation could result in undesirable results.\n\n14. An objective that can be met. It is used when a specific requirement is not feasible in some situations or with common current technology. Non- conformance to such requirements requires less justification and should be more readily approved.",
  "references": [
    "NIST SP 800-108r1 [August 2022 (Includes updates as of 02-02-2024)]; NIST SP 800-90B",
    "FIPS 186-5",
    "FIPS 203; FIPS 204; FIPS 205 from FIPS 186-5",
    "NIST SP 800-232",
    "NIST SP 800-227",
    "NIST SP 800-108 [Superseded]; NIST SP 800-135 Rev. 1; NIST SP 800-56A Rev. 2 [Superseded]; NIST SP 800-56B Rev. 2; NIST SP 800-56B Rev. 1 [Superseded]",
    "NIST SP 800-38F",
    "NIST SP 800-56C [Superseded]",
    "NIST SP 800-57 Part 1 Rev. 4 [Superseded]; NIST SP 800-57 Part 1 Rev. 5; NIST SP 800-57 Part 1 Rev. 3 [Superseded]",
    "NIST SP 800-89",
    "NIST SP 800-90A Rev. 1",
    "NIST SP 800-175B Rev. 1",
    "NIST SP 1800-15B from NIST SP 800-108; NIST SP 1800-15C from NIST SP 800-108",
    "NISTIR 5153",
    "NIST CSRC Glossary"
  ],
  "url": "https://mlchart.com/terminology/cybersecurity/should/"
}