Standard Background and Industry Value
This specification was jointly developed by the Science and Technology Department of the People's Bank of China, the four major state-owned commercial banks and leading technology companies, marking the entry of open source governance in my country's financial industry into the standardization implementation stage.
| Open source basic software | Operating system, database and other infrastructure | Linux, MySQL |
| Open source components | Middleware, development framework, etc. | Spring, Redis |
| Open source tools | Assisted development and operation tools | Jenkins, Prometheus |
Core evaluation indicator system
6.1 Introducing the evaluation three-dimensional model
Typical case: When a bank introduced the Kafka message queue, it needed to complete the following:
- Preliminary stage: Check the compliance of the Apache 2.0 license and verify the community activity (the number of commits in the past three months is ≥200)
- Final stage: Stress test TPS ≥ 500,000/second, verify the automatic switching time of cluster failure ≤ 30 seconds
7.2 Key indicators in the maintenance stage
| Evaluation dimensions | Simple use category | In-depth use category |
| Vulnerability response | High-risk vulnerabilities will be fixed within 72 hours | Possess vulnerability hot fix capability |
| Monitoring coverage | Basic operation indicator monitoring | Core algorithm performance monitoring |
Implementation recommendations
Organizational safeguards
- Establish an open source governance committee, with a joint review mechanism composed of technology, risk, and legal departments
- Build an open source software product library to achieve unified management of component versions (refer to clause 8.4)
Technical Implementation Route
- Toolchain Integration: Embed SCA tools (such as Black Duck) into CI/CD pipelines
- Automated Assessment: Develop assessment scripts based on specifications to automatically generate scoring reports for chapters 6.2-6.3
Best Practices: In the Redis upgrade assessment, a securities company passed:
- Compatibility testing: Verify the impact of API changes from version 6.0 to 7.0 (refer to 6.3.4)
- Performance comparison: Memory usage is reduced by 12% under the same load (refer to Table 10)