Page History

Content by Label

showLabels	false
maxResults	99
label	+fio,+rule,-void
showSpace	false
sort	title
space	com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@3bbaf8c
cql	label = "fio" and label = "rule" and label != "void" and space = currentSpace()

Info
Information for Editors To have a new guideline automatically listed above be sure to label it fio and rule.

Risk Assessment Summary

Rule	Severity	Likelihood	Detectable	Repairable	Priority	Level
FIO30-C	High	Likely	Yes	No	P18	L1
FIO32-C	Medium	Unlikely	No	No	P2	L3
FIO34-C	High	Probable	Yes	Yes	P18	L1
FIO37-C	High	Probable	Yes	Yes	P18	L1
FIO38-C	Low	Probable	Yes	No	P4	L3
FIO39-C	Low	Likely	Yes	No	P6	L2
FIO40-C	Low	Probable	Yes	Yes	P6	L2
FIO41-C	Low	Unlikely	Yes	Yes	P3	L3
FIO42-C	Medium	Unlikely	No	No	P2	L3
FIO44-C	Medium	Unlikely	No	No	P2	L3
FIO45-C	High	Probable	No	No	P6	L2
FIO46-C	Medium	Unlikely	No	No	P2	L3
FIO47-C	High	Unlikely	Yes	No	P6	L2

Related Rules and Recommendations

Navigation Map

	fio
	fio
cellWidth	700
wrapAfter	1
cellHeight	15

...

Image Added Image Added Image Added

C programs often rely on file to load or store data needed during program execution. File functions, such as open, read, write, and close are built into the C programming language itself to simplify how C programs interact with files and file data. By definition, the underlying operating system is responsible for managing access to files. This creates irregularities and inconsistencies between C programs and the underlying file system. Many of these descrepencies can lead to security vulnerabilities.

The following rules and recommendations are designed to reduce the common errors associated with file operations in C. These guidelines are designed to by system independent. However, files and file management is inherently tied to the underlying operating system. Cases where security issues or recomendations are specific to an architecture are clearly marked as pertaining to that architecture.