Sky Bear Technical Standards - Home
Search
×
FR

Placeholder headline

This is just a placeholder headline

ISO 21895:2026 Categorization and classification of civil uncrewed aircraft systems

$

129

BUY NOW

Placeholder headline

This is just a placeholder headline

ISO 9853:2026 Thermoplastics piping systems — Crushing test for moulded fittings

$

85

BUY NOW

Placeholder headline

This is just a placeholder headline

ISO 20915:2026 Life cycle inventory calculation methodology for steel products

$

347

BUY NOW

ISO 17961:2013

ISO 17961:2013 Information technology – Programming languages, their environments and system software interfaces – C secure coding rules

CDN $391.00

SKU: 11575759aa73 Category:

Description

ISO/IEC TS 17961:2013 specifies

  • rules for secure coding in the C programming language, and
  • code examples.

ISO/IEC TS 17961:2013 does not specify

  • the mechanism by which these rules are enforced, or
  • any particular coding style to be enforced.

Each rule in this Technical Specification is accompanied by code examples. 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.
Edition

1

Published Date

2013-11-15

Status

PUBLISHED

Pages

80

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

ISO/IEC TS 17961:2013 specifies

  • rules for secure coding in the C programming language, and
  • code examples.

ISO/IEC TS 17961:2013 does not specify

  • the mechanism by which these rules are enforced, or
  • any particular coding style to be enforced.

Each rule in this Technical Specification is accompanied by code examples. 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.

Previous Editions

Can’t find what you are looking for?

Please contact us at: