GA/T 1547-2019Information security technology - Security technical requirements and testing and evaluation methods for user data storage of mobile intelligent terminal (English PDF)

4.1 Classification of safety technical requirements

The security level required by mobile smart terminal user data storage security technology is in accordance with data storage, data access control, data backup and recovery the intensity of recovery, data destruction, and security auditing is divided into basic and enhanced levels.

4.2 Classification of safety technical requirements

This standard mainly proposes specific security technical requirements for each stage based on the life cycle of data storage of mobile intelligent terminal users, including Storage, data access control, data backup and recovery, data destruction and security audit.

5.1 Data storage

5.1.1 Storage media

Provide secure storage media and storage paths for user data.

a) User data should be stored in a non-volatile storage medium at power failure;

b) The user data generated by the subject should be stored in the default or set path.

5.1.2 Resource Control

The ability to allocate resources should be designed and implemented according to the following requirements.

a) can limit the storage resources occupied by user data generated by the application;

b) When the data storage space reaches the threshold, the mobile smart terminal operating system user can be alerted.

5.1.3 Defining data attributes

Data attributes should be defined by default or authorization configuration.

a) Basic attributes. generation time, last modification time, last access time, etc .;

b) Security attributes. owner, read/write permissions, data category, authorized subject and permissions, scope of use, etc .;

c) the importance of the data.

5.1.4 Data confidentiality

Measures should be taken to ensure the confidentiality of user data on mobile smart terminals.

a) Use password technology to ensure the confidentiality of user data when stored locally;

b) Encrypt and decrypt important user data using a cryptographic algorithm approved by the national cryptographic authority.

5.1.5 Data integrity

Protect and monitor the integrity of user data on mobile smart terminals.

a) Use verification technology or password technology to ensure the integrity of user data storage;

b) monitoring the integrity of user data, with clear prompts when integrity is breached;

c) adopting cryptographic technology to ensure the integrity of important user data during storage, and adopting cryptographic algorithms approved by the national password authority;

d) When integrity errors are detected, necessary recovery measures should be taken for user data.

5.2 Data access control

5.2.1 Access Control Policy

Should provide a default or definable access control policy.

a) The access control policy should include elements such as authorized subjects, access methods (read, write, delete, etc.) and objects;

b) the access control policy should cover all subjects, objects and operations between them;

c) an access control policy using the default prohibition principle;

d) Following the principle of least authorization, grant the entity the least necessary authority for the business.

5.2.2 Subject Identification and Identification

Before performing any operation on user data, authenticate or identify the subject.

a) When the operator is a person, his identity should be identified;

b) When the operating entity is an entity such as application software, its identity should be identified.

5.2.3 Access Control Based on Security Attributes

Access control based on security attributes should be provided, and only subjects allowed by the access control policy can perform corresponding operations on user data Make.

5.3 Data backup and recovery

Data backup and recovery functions should be provided for user data. Data backup includes copy backup or transfer backup.

a) Support local backup of user data through the peripheral interface of the mobile smart terminal, or remote backup via wireless network Share

b) The backup data should retain the basic and security attributes of the original data;

c) provide confidentiality and integrity protection for backup data;

d) support regular or periodic incremental or full backup strategies;

e) Ensure the availability of backup data and check the integrity of the data during recovery.

5.4 Data destruction

5.4.1 Data clear

When the mobile smart terminal restores factory settings, uninstalls applications, or otherwise needs to clear user data, it should be clearly reported Know the user.

5.4.2 Data self-destruction

Under certain conditions (such as continuous authentication failure, receiving corresponding instructions, etc.), the user data is automatically cleared.

5.4.3 Residual information protection

It should be ensured that unauthorized subjects cannot obtain the information content in the storage resources returned to the system after use by other subjects.

5.5 Security Audit

Entities that provide protection for user data (such as operating systems, application software) should provide security auditing functions for user data access, etc ..

a) The audit event type should at least include. data attribute definition operation, data authorization operation, data access behavior (including Failure and success), data backup and recovery, data destruction;

b) The contents of the audit event include at least. the date and time of the event, the identity of the subject, the type of operation, and the event result (success or failure)

c) Alert on potentially risky behaviors, such as storage space is about to run out, integrity checks fail, unauthorized access attempts Wait.

6.1 Data storage

6.1.1 Storage media

The test methods and expected results of the storage media are as follows.

a) Test method.

1) Generate or import user data through the operating system and application software;

2) Turn off the mobile smart terminal after power failure, and then turn on the mobile smart terminal to check whether the data is lost;

3) Check the data storage path by logging into the mobile smart terminal operating system.

b) Expected results.

1) The user data generated or imported by the operating system or application software is not lost after the mobile smart terminal is powered off and restarted;

2) User data is stored in the default or set path.

6.1.2 Resource control

The test methods and expected results of resource allocation are as follows.

a) Test method.

1) Limit the storage space occupied by certain types of data through mobile smart terminal settings;

2) Try to increase this type of data until the set limit is exceeded;

3) Check if the stored data exceeds the limit, whether an alarm can be performed and the set space limit is not exceeded.

b) Expected results.

1) Ability to limit the storage space occupied by applications;

2) When the storage space of the application and the storage space of the mobile smart terminal reach the limit, an alarm should be generated.

6.1.3 Defining data attributes

The test methods and expected results for defining data attributes are as follows.

a) Test method.

1) Obtain a mobile smart terminal privileged account and log in to the mobile smart terminal operating system with this account to view user data attributes;

2) Try to modify the security attributes of the data.

b) Expected results.

1) The data attributes include at least the requirements of basic attributes and security attributes;

2) Authorized users should be able to modify security attributes.

6.1.4 Data confidentiality

The test methods and expected results of data confidentiality are as follows.

a) Test method.

1) Add corresponding user data on the mobile smart terminal;

2) View the data on the memory through the binary reading tool and check whether it is in plain text;

3) The developer should provide documentation describing the type of cryptographic algorithm used.

b) Expected results.

1) The content read should be in plain text;

2) The type of cryptographic algorithm used is approved by the national cryptographic authority.

6.1.5 Data integrity

The data integrity test methods and expected results are as follows.

a) Test method.

1) Tamper with the stored data through other means (such as connecting the memory card to the computer, etc.), and then insert it into mobile smart Capable terminal

2) Access the tampered data from the mobile smart terminal and check if there is a prompt for integrity breach;

3) Attempt to recover user data whose integrity has been compromised;

4) The developer should provide documentation explaining the type of cryptographic algorithm adopted.

b) Expected results.

1) When the user's data integrity is damaged, inform the user in a clear way at the appropriate time;

2) Ability to recover user data whose integrity has been compromised;

3) The type of cryptographic algorithm used is approved by the national cryptographic authority.

6.2 Data access control

6.2.1 Access Control Policy

The test methods and expected results of the access control policy are as follows.

a) Test method.

1) Check whether the access control policy configuration covers the subject, object, and operation types between them;

2) Try access operations between different subjects and objects, and check whether the default policy is completely covered;

3) Install various application software newly, check whether the software can access other data under the default access control policy, or Whether other application software can access the data of the application software;

4) Check whether the access control policy adopts or supports the principle of least authorization to authorize the subject.

b) Expected results.

1) The access control policy covers all subjects, objects and operations between them;

2) Access control policy using the default prohibition principle;

3) The control strategy should adopt or support the principle of least authorization to authorize the subject.

6.2.2 Subject Identification and Identification

The test methods and expected results of subject identification and identification are as follows.

a) Test method.

1) Try to access the data as a user and check if it needs to be authenticated;

2) Set the access policy between each application software, check whether the authorized application software can access, and other application software does not have Law access.

b) Expected results.

1) When users access data, they must pass identity authentication;

2) Ability to identify authorized application software.

6.2.3 Access Control Based on Security Attributes

The test methods and expected results of data access control are as follows.

a) Test method.

1) Check whether the system has access control policies based on subject and data security attributes;

2) Try to access user data with different security attributes as different principals.

b) Expected results.

1) The operating system or application has or can set access control policies based on subject and data security attributes; the operating system or Applications have or can set access control policies based on subject and data security attributes;

2) Only principals allowed by the security policy can access the corresponding user data.

6.3 Data backup and recovery

The test methods and expected results of data backup and recovery are as follows.

a) Test method.

1) Through the peripheral interface of the mobile smart terminal, such as a USB data cable interface, a memory card interface, etc., or a wireless network, such as Mobile communication network, Wifi network, etc. to back up data;

2) After the backup is completed, check the backup file through the binary read tool;

3) After deleting the user data on the mobile smart terminal, try to recover the data and check the access rights of the recovered data;

4) Tamper with the content of the backup file and try to restore the data again;

5) Set different backup policies and check whether the backup is performed according to the set policies.

b) Expected results.

1) Can support local backup or remote backup;

2) The backup file is stored in an encrypted manner;

3) Supports the restoration of backup data, and the data attributes remain in the state before backup after the restoration;

4) After the integrity of the backup file is damaged, corresponding prompts can be given during recovery;

5) Able to support various backup strategies and install the set strategy for backup.

6.4 Data destruction

6.4.1 Data Clear

The test methods and expected results of data erasure are as follows.

a) Test method.

1) Attempt to restore the factory settings of the mobile smart terminal and check whether the user will be clearly notified and the user data will be cleared;

2) Try uninstalling the application with user data, check whether the user is explicitly informed, whether the user data needs to be cleared, select when deciding to clear the data, check whether the data and information generated by it can be deleted.

b) Expected results. When user data needs to be cleared, the user should be clearly informed.

6.4.2 Data self-destruction

The test methods and expected results of data self-destruction are as follows.

a) Test method.

1) Check whether the mobile smart terminal has the user data self-destruct function;

2) Set the conditions for data self-destruction, such as the number of authentication failures, unsuccessful connection to the background for a long time, and setting instructions through the background;

3) Trigger the data self-destruct condition, read the data in the memory with the tool, and check whether the data has been cleared.

b) Expected results.

1) Mobile smart terminal has user data self-destruct function;

2) Data self-destruction has strict trigger conditions.

6.4.3 Residual information protection

The test methods and expected results of residual information protection are as follows.

a) Test method.

1) Clear user data through active deletion and data self-destruction;

2) Use the data recovery tool to try to recover the deleted data in the memory and check whether the data has been erased.

b) Expected results. User data erased by active deletion and data self-destruction cannot be retrieved through data recovery tools.

6.5 Security audit

The test methods and expected results of the security audit are as follows.

a) Test method.

1) Try to define data attributes, perform authorized operations on the data, authorized and unauthorized data access, data backup and recovery Operations such as data recovery, data deletion and destruction, and data integrity damage;

2) Check whether there are corresponding audit records and the content of the audit records is correct.

b) Expected results.

1) Ability to audit the main operating behaviors for user data;

2) The audit content includes the date and time of the event, the identity of the subject, the type of operation, and the outcome of the event (success or failure)

3) Be able to alert in time to actions with potential risks.