UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

close
Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

close
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Webinars & White Papers

CSA ISO/IEC TS 17961

Information technology - Programming languages, their environments and system software interfaces - C secure coding rules

active, Most Current
Buy Now
Organization: CSA
Publication Date: 1 January 2018
Status: active
Page Count: 104
ICS Code (Languages used in information technology): 35.060
scope:

This Technical Specification specifies

- rules for secure coding in the C programming language and

- code examples.

This Technical Specification does not specify

- the mechanism by which these rules are enforced or

- any particular coding style to be enforced. (It has been impossible to develop a consensus on appropriate style guidelines. Programmers should define style guidelines and apply these guidelines consistently. The easiest way to consistently apply a coding style is with the use of a code formatting tool. Many interactive development environments provide such capabilities.)

Each rule in this Technical Specification is accompanied by code examples. Code examples are informative only and serve to clarify the requirements outlined in the normative portion of the rule. Examples impose no normative requirements.

Each rule in this Technical Specification that is based on undefined behavior defined in the C Standard identifies the undefined behavior by a numeric code. The numeric codes for undefined behaviors can be found in Annex B, Undefined Behavior.

Two distinct kinds of examples are provided:

- noncompliant examples demonstrating language constructs that have weaknesses with potentially exploitable security implications; such examples are expected to elicit a diagnostic from a conforming analyzer for the affected language construct; and

- compliant examples are expected not to elicit a diagnostic. Examples are not intended to be complete programs. For brevity, they typically omit #include directives of C Standard Library headers that would otherwise be necessary to provide declarations of referenced symbols. Code examples may also declare symbols without providing their definitions if the definitions are not essential for demonstrating a specific weakness.

Some rules in this Technical Specification have exceptions. Exceptions are part of the specification of these rules and are normative.

Document History

CSA ISO/IEC TS 17961
January 1, 2018
Information technology - Programming languages, their environments and system software interfaces - C secure coding rules
This Technical Specification specifies — rules for secure coding in the C programming language and — code examples. This Technical Specification does not specify — the mechanism by which these...

References

Advertisement