Search book title
Enter keywords for book title search
Search book content
Enter keywords for book content search
Filters:
FORMAT
BOOKS
PACKAGES
EDITION
to
PUBLISHER
(1)
(326)
(573)
(44)
(234)
(969)
(652)
(2114)
(64)
(92448)
(54)
(541)
(117)
(33)
(20)
(19)
(93277)
(3)
(17)
(1)
(351)
(300)
(6217)
(240)
(16)
(5)
(1621)
(16)
(19)
(28)
(4)
 
(6)
(7)
(115)
(3)
(57)
(5)
(5)
(1)
(1)
(2)
(25)
(26)
(27)
(13)
(61)
(24)
(22)
(7)
(8)
(20)
(1)
(3)
(50)
(6)
(31)
CONTENT TYPE
 Act
 Admin Code
 Announcements
 Bill
 Book
 CADD File
 CAN
 CEU
 Charter
 Checklist
 City Code
 Code
 Commentary
 Comprehensive Plan
 Conference Paper
 County Code
 Course
 DHS Documents
 Document
 Errata
 Executive Regulation
 Federal Guideline
 Firm Content
 Guideline
 Handbook
 Interpretation
 Journal
 Land Use and Development
 Law
 Legislative Rule
 Local Amendment
 Local Code
 Local Document
 Local Regulation
 Local Standards
 Manual
 Model Code
 Model Standard
 Notice
 Ordinance
 Other
 Paperback
 PASS
 Periodicals
 PIN
 Plan
 Policy
 Product
 Program
 Provisions
 Requirements
 Revisions
 Rules & Regulations
 Standards
 State Amendment
 State Code
 State Manual
 State Plan
 State Standards
 Statute
 Study Guide
 Supplement
 Technical Bulletin
 All
  • BSI
    PD ISO/IEC TS 17961:2013 Information technology. Programming languages, their environments and system software interfaces. C secure coding rules
    Edition: 2016
    $538.63
    / user per year

Description of PD ISO/IEC TS 17961:2013 2016

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.



About BSI

BSI Group, also known as the British Standards Institution is the national standards body of the United Kingdom. BSI produces technical standards on a wide range of products and services and also supplies certification and standards-related services to businesses.

X