| /trusted-firmware-a/docs/security_advisories/ |
| A D | index.rst | 9 security-advisory-tfv-1.rst
10 security-advisory-tfv-2.rst
11 security-advisory-tfv-3.rst
12 security-advisory-tfv-4.rst
13 security-advisory-tfv-5.rst
14 security-advisory-tfv-6.rst
15 security-advisory-tfv-7.rst
16 security-advisory-tfv-8.rst
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/security_advisories/ |
| A D | index.rst.txt | 9 security-advisory-tfv-1.rst
10 security-advisory-tfv-2.rst
11 security-advisory-tfv-3.rst
12 security-advisory-tfv-4.rst
13 security-advisory-tfv-5.rst
14 security-advisory-tfv-6.rst
15 security-advisory-tfv-7.rst
16 security-advisory-tfv-8.rst
|
| /trusted-firmware-a/plat/layerscape/common/ |
| A D | ls_tzc380.c | 19 unsigned int security, unsigned int subreg_disable_mask) in tzc380_set_region() argument
29 mmio_write_32((uintptr_t)reg, ((security & 0xF) << 28)); in tzc380_set_region()
39 attr_value = ((security & 0xF) << 28) | in tzc380_set_region()
|
| /trusted-firmware-a/docs/process/ |
| A D | index.rst | 9 security
17 security-hardening
|
| A D | security.rst | 7 We disclose all security vulnerabilities we find, or are advised about, that are
13 issues in the project's `issue tracker`_ with the ``security-advisory`` tag. You
21 community of developers and security researchers.
24 If you think you have found a security vulnerability, please **do not**
26 follow the `TrustedFirmware.org security incident process`_.
40 with the source code and in any published security advisory.
85 .. _TrustedFirmware.org security incident process: https://developer.trustedfirmware.org/w/collabor…
|
| 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
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/process/ |
| A D | index.rst.txt | 9 security
17 security-hardening
|
| A D | security.rst.txt | 7 We disclose all security vulnerabilities we find, or are advised about, that are
13 issues in the project's `issue tracker`_ with the ``security-advisory`` tag. You
21 community of developers and security researchers.
24 If you think you have found a security vulnerability, please **do not**
26 follow the `TrustedFirmware.org security incident process`_.
40 with the source code and in any published security advisory.
85 .. _TrustedFirmware.org security incident process: https://developer.trustedfirmware.org/w/collabor…
|
| A D | security-hardening.rst.txt | 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
|
| /trusted-firmware-a/include/common/ |
| A D | ep_info.h | 37 #define SET_SECURITY_STATE(x, security) \ argument
38 ((x) = ((x) & ~EP_SECURITY_MASK) | (security))
|
| /trusted-firmware-a/plat/nvidia/tegra/soc/t186/drivers/se/ |
| 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()
|
| /trusted-firmware-a/plat/nvidia/tegra/soc/t194/drivers/se/ |
| 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()
|
| /trusted-firmware-a/docs/design/ |
| A D | interrupt-framework-design.rst | 36 Secure-EL1 depending upon the security state of the current execution
76 either security state.
183 This applies when execution is in either security state.
250 security state.
264 security state. EL3 interrupts are not considered.
334 for the security state specified in the ``flags`` parameter.
525 is used to generate non-secure interrupts in either security state.
676 structure for the target security state.
681 ``cpu_context_t`` data structure for the target security state.
706 could use the security state flag to check this.
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | interrupt-framework-design.rst.txt | 36 Secure-EL1 depending upon the security state of the current execution
76 either security state.
183 This applies when execution is in either security state.
250 security state.
264 security state. EL3 interrupts are not considered.
334 for the security state specified in the ``flags`` parameter.
525 is used to generate non-secure interrupts in either security state.
676 structure for the target security state.
681 ``cpu_context_t`` data structure for the target security state.
706 could use the security state flag to check this.
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/threat_model/ |
| A D | threat_model.rst.txt | 200 | | security implications | |
332 | | when the security check is produced before the time |
407 | | conditional branches that are security sensitive, |
547 | | multiple points where memory corruption security |
549 | | security issue since it could allow an attacker |
593 | | sanitized before being used. These security checks |
651 | | security boundaries. An attacker might attempt to |
692 | | execute code if the proper security mechanisms |
780 .. _STRIDE threat analysis technique: https://docs.microsoft.com/en-us/azure/security/develop/threa…
782 .. _Cache Speculation Side-channels: https://developer.arm.com/support/arm-security-updates/specula…
[all …]
|
| /trusted-firmware-a/docs/threat_model/ |
| A D | threat_model.rst | 200 | | security implications | |
332 | | when the security check is produced before the time |
407 | | conditional branches that are security sensitive, |
547 | | multiple points where memory corruption security |
549 | | security issue since it could allow an attacker |
593 | | sanitized before being used. These security checks |
651 | | security boundaries. An attacker might attempt to |
692 | | execute code if the proper security mechanisms |
780 .. _STRIDE threat analysis technique: https://docs.microsoft.com/en-us/azure/security/develop/threa…
782 .. _Cache Speculation Side-channels: https://developer.arm.com/support/arm-security-updates/specula…
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/about/ |
| A D | features.rst.txt | 64 security services.
118 - Ongoing security hardening, optimization and quality improvements.
123 .. _Trusty Secure OS: https://source.android.com/security/trusty
|
| /trusted-firmware-a/docs/about/ |
| A D | features.rst | 64 security services.
118 - Ongoing security hardening, optimization and quality improvements.
123 .. _Trusty Secure OS: https://source.android.com/security/trusty
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | activity-monitors.rst.txt | 22 As a security precaution, Trusted Firmware-A does not enable these by default.
|
| /trusted-firmware-a/docs/components/spd/ |
| A D | trusty-dispatcher.rst | 9 https://source.android.com/security/trusty
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/spd/ |
| A D | trusty-dispatcher.rst.txt | 9 https://source.android.com/security/trusty
|
| /trusted-firmware-a/docs/components/ |
| A D | activity-monitors.rst | 22 As a security precaution, Trusted Firmware-A does not enable these by default.
|
| /trusted-firmware-a/docs/plat/marvell/armada/misc/ |
| A D | mvebu-iob.rst | 10 the enabled windows. If there is a hit and it passes the security checks, it is
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/marvell/armada/misc/ |
| A D | mvebu-iob.rst.txt | 10 the enabled windows. If there is a hit and it passes the security checks, it is
|
| /trusted-firmware-a/docs/perf/ |
| 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.
|