Update Software, Dependencies and End of Life

Get Started. It's Free
or sign up with your email address
Update Software, Dependencies and End of Life by Mind Map: Update Software, Dependencies and End of Life

1. ioXt Alliance

1.1. Mobile Application Profile

1.1.1. 4.5. Verified Software VS1

1.1.2. 4.6. Security by Default SD115

1.1.3. 4.8. Automatically Applied Updates AA1

1.1.4. 4.8. Automatically Applied Updates AA2

1.1.5. 4.8. Automatically Applied Updates AA3

1.1.6. 4.8. Automatically Applied Updates AA4

1.1.7. "4.10. Security Expiration Date SE1.1"

1.1.8. "4.10. Security Expiration Date SE1.2"

2. GOOGLE

2.1. Core app quality

2.1.1. PS-T1

2.1.2. PS-T2

2.1.3. PS-T3

2.1.4. PS-T4

2.2. App Security Best Practices

2.2.1. Keep services and dependencies up-to-date

2.2.2. Keep services and dependencies up-to-date Check the Google Play services security provider

2.2.3. Keep services and dependencies up-to-date Update all app dependencies

3. Department for Digital, Culture, Media & Sport (DCMS)

3.1. Code of practice for app store operators and app developers

3.1.1. 1. Ensure only apps that meet the code’s security and privacy baseline requirements are allowed on the app store

3.1.2. 2. Ensure apps adhere to baseline security and privacy requirements

3.1.3. 4. Keep apps updated to protect users

3.1.4. 4. Keep apps updated to protect users

3.1.5. 4. Keep apps updated to protect users

3.1.6. 4. Keep apps updated to protect users

3.1.7. 5. Provide important security and privacy information to users in an accessible way

3.1.8. 6. Provide security and privacy guidance to Developers

4. US National Institute of Standards and Technology (NIST)

4.1. NIST Special Publication 800-190

4.1.1. 4.5.3 Host OS component vulnerabilities

4.1.2. 6.4 Operations and Maintenance Phase

5. National Information Assurance Partnership (NIAP)

5.1. Requirements for Vetting Mobile Apps from the Protection Profile for Application Software

5.1.1. Integrity for Installation and Update FPT_TUD_EXT.1.1

5.1.2. Integrity for Installation and Update FPT_TUD_EXT.1.5

5.1.3. Security Assurance Requirements ATE_IND.1.2E

5.1.4. Security Assurance Requirements AVA_VAN.1.1C

5.1.5. Integrity for Installation and Update FPT_TUD_EXT.2.1

5.1.6. Integrity for Installation and Update FPT_TUD_EXT.2.2

6. APPLE

6.1. Developer Security

6.1.1. Secure Code Updating Mac Software Overview

6.1.2. Secure Code Updating Mac Software Update Files that Include Signed Code

6.1.3. Secure Code Updating Mac Software Check Third-Party Software Updaters

7. European Telecommunications Standards Institute (ETSI)

7.1. ETSI TS 103 732

7.1.1. 8.1.1 Cryptographic Support (FCS) FCS_COP.1_Update Cryptographic operation

7.1.2. 8.1.2.1 The Update Policy FDP_ACC.1_Update Subset access control

7.1.3. 8.1.2.1 The Update Policy FDP_ACF.1_Update Security attribute based access control

7.1.4. 8.1.2.2 The Permissions Policy FDP_ACF.1_Permissions Security attribute based access control

7.1.5. 8.1.2.3 The Data Classification Policy FDP_ACF.1_User_Data_Asset_Decryption Security attribute based access control

7.1.6. 8.1.4 Security Management (FMT) FMT_SMF.1_Update Specification of Management Functions

7.1.7. 8.1.6 Protection of the TSF (FPT) FPT_FLS.1 Failure with preservation of secure state

8. Open Web Application Security Project (OWASP)

8.1. Mobile Application Security Verification Standard (MASVS)

8.1.1. 1.9 MSTG-ARCH-9

8.1.2. 5.6 MSTG-NETWORK-6

8.2. Application Security Verification Standard 4.0.3 (ASVS)

8.2.1. V1.14 Configuration Architecture

8.2.2. V10.3 Application Integrity

8.2.3. V14.2 Dependency