This section is under construction.
Information for Editors
To have a new guideline automatically listed above be sure to label it api and recommendation.
Risk Assessment Summary
How does one suggest a new rule? I'd like to suggest API10-C. APIs should have security options enabled by default
If the caller of this API doesn't understand what the options mean, they will pass 0 or TLS_DEFAULT_OPTIONS and get a connection vulnerable to man-in-the-middle attacks and using old versions of TLS.
If the caller of this API doesn't understand the options and passes 0 or TLS_DEFAULT_OPTIONS they will get certificate validation with only the current version of TLS enabled.
This API design principle can be extended to cover other security properties – for example, having best practice cipher suites enabled by default (something that changes over time) while disabling out-of-favor cipher suites by default. When interface stability is also a design requirement, an interface can meet both goals by providing off-by-default options that produce stable behavior, such as TLS_ENABLE_Y2015_BEST_PRACTICE_CIPHERS_ONLY.
seems like a reasonable recommendation; possibly difficult to enforce. i'll try to add something.
OK, stubbed out as API02-C. APIs should have security options enabled by default
only for completeness: In table "Risk Assessment Summary" the items API02-C, API05-C and API10-C are missing. Please correct.