Application Programming Interfaces (API)
Warning
This section is under construction.
- API00-C. Functions should validate their parameters
- API01-C. Avoid laying out strings in memory directly before sensitive data
- API02-C. Functions that read or write to or from an array should take an argument to specify the source or target size
- API03-C. Create consistent interfaces and capabilities across related functions
- API04-C. Provide a consistent and usable error-checking mechanism
- API05-C. Use conformant array parameters
- API07-C. Enforce type safety
- API09-C. Compatible values should have the same type
- API10-C. APIs should have security options enabled by default
Information for Editors
To have a new guideline automatically listed above be sure to label it api and recommendation .
Risk Assessment Summary
| Rule | Severity | Likelihood | Detectable | Repairable | Priority | Level |
|---|---|---|---|---|---|---|
| API00-C | Medium | Unlikely | No | No | P2 | L3 |
| API01-C | High | Likely | Yes | No | P18 | L1 |
| API02-C | High | Likely | Yes | No | P18 | L1 |
| API03-C | Medium | Unlikely | No | No | P2 | L3 |
| API04-C | Medium | Unlikely | No | No | P2 | L3 |
| API05-C | High | Probable | Yes | No | P12 | L1 |
| API07-C | Medium | Unlikely | No | No | P2 | L3 |
| API09-C | Low | Unlikely | No | No | P1 | L3 |
| API10-C | Medium | Likely | No | No | P6 | L3 |
