| /rk3399_ARM-atf/docs/security_advisories/ |
| H A D | index.rst | 8 security-advisory-tfv-1.rst
9 security-advisory-tfv-2.rst
10 security-advisory-tfv-3.rst
11 security-advisory-tfv-4.rst
12 security-advisory-tfv-5.rst
13 security-advisory-tfv-6.rst
14 security-advisory-tfv-7.rst
15 security-advisory-tfv-8.rst
16 security-advisory-tfv-9.rst
17 security-advisory-tfv-10.rst
[all …]
|
| H A D | security-advisory-tfv-9.rst | 32 This security advisory describes the current understanding of the Trusted
118 .. _Arm Processor Security Update: http://www.arm.com/security-update
121 .. _CVE-2022-23960 mitigation specification: https://developer.arm.com/support/arm-security-updates…
|
| H A D | security-advisory-tfv-6.rst | 28 This security advisory describes the current understanding of the Trusted
145 Refer to :ref:`security-advisory-tfv-7` for further details on this variant.
149 Refer to :ref:`security-advisory-tfv-9` for further details on this variant.
152 .. _Arm Processor Security Update: http://www.arm.com/security-update
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | index.rst | 8 security
17 security-hardening
|
| H A D | security.rst | 7 We disclose all security vulnerabilities we find, or are advised about, that are
19 community of developers and security researchers.
22 If you think you have found a security vulnerability, please **do not**
24 follow the `TrustedFirmware.org security incident process`_.
38 with the source code and in any published security advisory.
94 .. _TrustedFirmware.org security incident process: https://trusted-firmware-docs.readthedocs.io/en/…
|
| H A D | security-hardening.rst | 4 This page contains guidance on what to check for additional security measures,
5 including build options that can be modified to improve security or catch issues
11 Part of the security of a platform is handling errors correctly, as described in
12 the previous section. There are several other security considerations covered in
124 Several build options can be used to check for security issues. Refer to the
138 Additional guidelines are provided below for some security-related build
143 console. Keeping this feature enabled is considered dangerous from a security
|
| /rk3399_ARM-atf/include/common/ |
| H A D | ep_info.h | 37 #define SET_SECURITY_STATE(x, security) \ argument
38 ((x) = ((x) & ~EP_SECURITY_MASK) | (security))
|
| /rk3399_ARM-atf/plat/nvidia/tegra/soc/t186/drivers/se/ |
| H A D | se.c | 244 uint32_t val = 0U, hash_offset = 0U, scratch_offset = 0U, security; in tegra_se_save_sha256_hash() local
250 security = tegra_se_read_32(SE0_SECURITY); in tegra_se_save_sha256_hash()
251 tegra_se_write_32(SE0_SECURITY, security | SE0_SECURITY_SE_SOFT_SETTING); in tegra_se_save_sha256_hash()
262 tegra_se_write_32(SE0_SECURITY, security); in tegra_se_save_sha256_hash()
|
| /rk3399_ARM-atf/plat/nvidia/tegra/soc/t194/drivers/se/ |
| H A D | se.c | 414 uint32_t security; in tegra_se_calculate_save_sha256() local
420 security = tegra_se_read_32(SE0_SECURITY); in tegra_se_calculate_save_sha256()
421 tegra_se_write_32(SE0_SECURITY, security | SE0_SECURITY_SE_SOFT_SETTING); in tegra_se_calculate_save_sha256()
438 tegra_se_write_32(SE0_SECURITY, security); in tegra_se_calculate_save_sha256()
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | context-management-library.rst | 12 software running in various security states (Secure/Non-Secure/Realm).
14 are not banked per world. When moving between the security states it is the
28 security state and save enough EL3 metadata to be able to return to that exception
29 level and security state. The memory for the context data structures are allocated
33 security states (Non-Secure, Secure, Realm). Each world must have its
34 configuration of system registers independent of other security states to access
37 If the CPU switches across security states (for example: from Non-secure to Secure
41 the architectural features enabled in the former security state will be unconditionally
42 accessible in the latter security state as well. This can be a major concern when
43 dealing with security-specific bits, as they need to be explicitly enabled or
[all …]
|
| H A D | activity-monitors.rst | 22 As a security precaution, Trusted Firmware-A does not enable these by default.
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | index.rst | 14 current status of the code from a security standpoint.
41 .. _STRIDE threat modeling technique: https://docs.microsoft.com/en-us/azure/security/develop/threa…
|
| H A D | threat_model_arm_cca.rst | 31 recommended by `Arm CCA security model`_:
34 *hardware enforced security (CCA HES).*
40 These are requirements of the `Arm CCA security model`_:
44 *[R0149] Any monitor data that may affect the CCA security guarantee, other*
56 This is a requirement of the `Arm CCA security model`_:
68 These are requirements of the `Arm CCA security model`_:
|
| H A D | threat_model.rst | 46 bare-minimum security prerequisites for System-on-Chips (SoC).
169 analysis side-channel attacks represent a category of security threats that
231 | | security implications | |
423 | | where memory corruption security errors can arise. |
459 | | sanitized before being used. These security checks |
497 | | execute code if the proper security mechanisms |
640 | | other security-sensitive processes. By observing |
799 | | when the security check is produced before the time |
888 | | branches that are security sensitive, can be used |
950 environment's security.
[all …]
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | drtm_poc.rst | 13 enable enforcing security policies.
21 the security of the system.
39 system’s state, measures security-critical attributes of the system,
|
| H A D | dtpm_drivers.rst | 7 performing security-related operations.
16 TPM measurements establish the security posture of a system and are used for
18 a security standpoint because it ensures hardware-backed attestation earlier
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | interrupt-framework-design.rst | 36 Secure-EL1 depending upon the security state of the current execution
40 Secure-EL1, Non-secure EL1 or EL2 depending upon the security state of the
45 depending upon the security state of the current execution context. It is
66 FEL. This register is configured independently by EL3 software for each security
67 state prior to entry into a lower exception level in that security state.
70 its target exception level for each security state. It is represented by a
71 single bit for each security state. A value of ``0`` means that the interrupt
76 either security state.
174 FIQ or IRQ signal to the CPU depending upon the current security state. The
183 This applies when execution is in either security state.
[all …]
|
| /rk3399_ARM-atf/docs/components/spd/ |
| H A D | trusty-dispatcher.rst | 9 https://source.android.com/security/trusty
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/misc/ |
| H A D | mvebu-iob.rst | 10 the enabled windows. If there is a hit and it passes the security checks, it is
|
| /rk3399_ARM-atf/docs/plat/st/ |
| H A D | stm32mp2.rst | 28 Each line comes with a security option (cryptography & secure boot) and a Cortex-A frequency option:
43 Each line comes with a security option (cryptography & secure boot) and a Cortex-A frequency option:
59 Each line comes with a security option (cryptography & secure boot) and a Cortex-A frequency option:
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | performance-monitoring-unit.rst | 8 implementation and to complement the PMU security guidelines given in the
122 security state unless it is enabled here.
|
| /rk3399_ARM-atf/plat/intel/soc/common/drivers/ccu/ |
| H A D | ncore_ccu.h | 309 CCU_REGION_SECURITY_t security, CCU_REGION_PRIVILEGE_t privilege);
336 CCU_REGION_SECURITY_t security, CCU_REGION_PRIVILEGE_t privilege);
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | features.rst | 80 security services.
145 - Ongoing security hardening, optimization and quality improvements.
150 .. _Trusty Secure OS: https://source.android.com/security/trusty
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | s32g274a.rst | 5 security, high-performance real-time and application processing and network
14 applications, high-performance processing, safety and security applications.
|
| /rk3399_ARM-atf/docs/ |
| H A D | index.rst | 45 Users are encouraged to do their own security validation, including penetration
66 and process, how security disclosures are handled, and the guidelines for
|