Lines Matching full:security

7 emphasis on security.
17 security is addressed within the Zephyr project.  All code submitted
26 security perspective.  Many of the ideas contained herein are captured
37 need to have.  This section gives references to other security
46 documentation about how security-sensitive issues are handled by the
58 help prevent security violations and limit their impact:
63   security measures, publicly accepted cryptographic algorithms and
79   to provide maximum security.  This corresponds to the "Secure by
89   positive security model aims to minimize the attack surface of the
98 - **Psychological acceptability** requires that security features are
105 - **Complementary Security/Defense in Depth**: do not rely on a single
106   threat mitigation approach. In case of the complementary security
156 - open design (security mechanisms should not depend on attacker
227 Zephyr Security Subcommittee
230 There shall be a "Zephyr Security Subcommittee", responsible for
242 developer shall determine if this change affects the security of the
243 system (based on their general understanding of security), and if so,
247 mainline code until the security issues have been addressed.
258 Because security issues are often sensitive, this issue tracking
259 system shall have a field to indicate a security issue.  Setting this
260 field shall result in the issue only being visible to the Zephyr Security
262 field to allow the Zephyr Security Subcommittee to add additional users that will
267 because security considerations are often external to the Zephyr
272 Zephyr Security Subcommittee.  This review should focus on
282 Changes to this document shall be reviewed by the Zephyr Security Subcommittee,