 MITRE Defense Agile Acquisition Guide - Mar 2014monthly. These frequent iterations effectively measure progress, reduce technical and programmatic risk, and respond to feedback and changes more quickly than traditional methods. Programs can adopt understand and appreciate each stakeholder’s risk tolerance and legal responsibilities, and provide clear and compelling evidence that an Agile approach can reduce risk. Application of Agile practices may appear appear at first glance to encroach upon traditional DoD risk reduction practices, which are optimized for weapon systems acquisition. These traditional methods most often involve extensive analysis, planning0 码力 | 74 页 | 3.57 MB | 5 月前3 MITRE Defense Agile Acquisition Guide - Mar 2014monthly. These frequent iterations effectively measure progress, reduce technical and programmatic risk, and respond to feedback and changes more quickly than traditional methods. Programs can adopt understand and appreciate each stakeholder’s risk tolerance and legal responsibilities, and provide clear and compelling evidence that an Agile approach can reduce risk. Application of Agile practices may appear appear at first glance to encroach upon traditional DoD risk reduction practices, which are optimized for weapon systems acquisition. These traditional methods most often involve extensive analysis, planning0 码力 | 74 页 | 3.57 MB | 5 月前3
 Istio Security Assessmentgoal of the assessment was to identify security issues related to the Istio code base, highlight high risk configurations commonly used by administrators, and provide perspective on whether security features Confidential Table of Findings For each finding, NCC Group uses a composite risk score that takes into account the severity of the risk, application’s exposure and user population, technical difficulty of exploitation exploitation, and other factors. For an explanation of NCC Group’s risk rating and finding categorization, see Appendix A on page 38. Title ID Risk Inability To Secure Control Plane Network Communications0 码力 | 51 页 | 849.66 KB | 1 年前3 Istio Security Assessmentgoal of the assessment was to identify security issues related to the Istio code base, highlight high risk configurations commonly used by administrators, and provide perspective on whether security features Confidential Table of Findings For each finding, NCC Group uses a composite risk score that takes into account the severity of the risk, application’s exposure and user population, technical difficulty of exploitation exploitation, and other factors. For an explanation of NCC Group’s risk rating and finding categorization, see Appendix A on page 38. Title ID Risk Inability To Secure Control Plane Network Communications0 码力 | 51 页 | 849.66 KB | 1 年前3
 A Security Guide for Kotlin Developers.............2 Most Common Security Attacks...............................3 Top Kotlin Security Risk...........................................5 OWASP Mobile TOP 10 Mobile Risks.................... of the right flags to the right pieces of code to minimize attack vectors. So, for this security risk, it’s a matter of diligent and defensive coding with mindful policies within the developer team as automatic identification, so that the quick fixes can be applied without hassle. Top Kotlin Security Risk #1: Improper Control of Resources Through Their Lifetimes 6 Kiuwan | Security Guide for Kotlin0 码力 | 13 页 | 1.80 MB | 1 年前3 A Security Guide for Kotlin Developers.............2 Most Common Security Attacks...............................3 Top Kotlin Security Risk...........................................5 OWASP Mobile TOP 10 Mobile Risks.................... of the right flags to the right pieces of code to minimize attack vectors. So, for this security risk, it’s a matter of diligent and defensive coding with mindful policies within the developer team as automatic identification, so that the quick fixes can be applied without hassle. Top Kotlin Security Risk #1: Improper Control of Resources Through Their Lifetimes 6 Kiuwan | Security Guide for Kotlin0 码力 | 13 页 | 1.80 MB | 1 年前3
 Dapr july 2020 security audit reportinvocation request, the unsanitized parameter is concatenated onto the targeted URL. This introduces the risk of attackers passing HTTP parameters into the method parameter, which are then appended to secrets of statestore components can be received from Dapr via the getSecrets API. This introduces the risk of attackers extracting passwords and sensitive secrets to authenticate at statestore components, handlers of topic routes which are out-of-scope for the publishing Dapr sidecar. This highlights the risk of attackers bypassing the PubSub component entirely, invoking the event routes for topics which are0 码力 | 19 页 | 267.84 KB | 1 年前3 Dapr july 2020 security audit reportinvocation request, the unsanitized parameter is concatenated onto the targeted URL. This introduces the risk of attackers passing HTTP parameters into the method parameter, which are then appended to secrets of statestore components can be received from Dapr via the getSecrets API. This introduces the risk of attackers extracting passwords and sensitive secrets to authenticate at statestore components, handlers of topic routes which are out-of-scope for the publishing Dapr sidecar. This highlights the risk of attackers bypassing the PubSub component entirely, invoking the event routes for topics which are0 码力 | 19 页 | 267.84 KB | 1 年前3
 OpenAI 《A practical guide to building agents》speech, harassment, violence) to maintain safe, respectful interactions. Tool safeguards Assess the risk of each tool available to your agent by assigning a rating—low, medium, or high—based on factors permissions, and financial impact. Use these risk ratings to trigger automated actions, such as pausing for guardrail checks before executing high-risk functions or escalating to a human if needed. "Churn Detection Agent" "Identify if the user message indicates a potential customer churn risk." agents Agent, GuardrailFunctionOutput, InputGuardrailTripwireTriggered, RunContextWrapper0 码力 | 34 页 | 7.00 MB | 6 月前3 OpenAI 《A practical guide to building agents》speech, harassment, violence) to maintain safe, respectful interactions. Tool safeguards Assess the risk of each tool available to your agent by assigning a rating—low, medium, or high—based on factors permissions, and financial impact. Use these risk ratings to trigger automated actions, such as pausing for guardrail checks before executing high-risk functions or escalating to a human if needed. "Churn Detection Agent" "Identify if the user message indicates a potential customer churn risk." agents Agent, GuardrailFunctionOutput, InputGuardrailTripwireTriggered, RunContextWrapper0 码力 | 34 页 | 7.00 MB | 6 月前3
 2021 中国开源年度报告entire world. With great powers comes great responsibility. The wider the application, the higher the risk. How should we think about and secure the open source supply chain? How should we build a healthier open source repositories on the Gitee platform, and the results showed that over 93% were not at risk for CVE vulnerabilities. 其中,在所有存在 CVE 漏洞风险的项目中,存在一个 CVE 漏洞的占比为 18.51%,存在超 过 10 个 CVE 漏洞的占比 2 为 44.21%。 Of the projects with direct license conflicts, 44.21% had only one Lincense conflict risk. 3.总结 Summary 2021 年,国内开源生态发展稳中向好,参与开源的人数随着开发者基数越来越多,优质开源 项目的数量与种类越来越丰富,大厂开源项目与普通开发者的开源项目齐头并进,在高速发展0 码力 | 199 页 | 9.63 MB | 1 年前3 2021 中国开源年度报告entire world. With great powers comes great responsibility. The wider the application, the higher the risk. How should we think about and secure the open source supply chain? How should we build a healthier open source repositories on the Gitee platform, and the results showed that over 93% were not at risk for CVE vulnerabilities. 其中,在所有存在 CVE 漏洞风险的项目中,存在一个 CVE 漏洞的占比为 18.51%,存在超 过 10 个 CVE 漏洞的占比 2 为 44.21%。 Of the projects with direct license conflicts, 44.21% had only one Lincense conflict risk. 3.总结 Summary 2021 年,国内开源生态发展稳中向好,参与开源的人数随着开发者基数越来越多,优质开源 项目的数量与种类越来越丰富,大厂开源项目与普通开发者的开源项目齐头并进,在高速发展0 码力 | 199 页 | 9.63 MB | 1 年前3
 openEuler OS Technical Whitepaper
Innovation Projects
(June, 2023)interactions between the REE and TEE and big data interaction. secGear architecture Scenario Financial risk control Hardware security module alternative Fully-encrypted database with software and hardware System performance diagnosis: TCP and I/O performance jitter diagnosis in common scenarios. • System risk inspection: Second-level inspection on kernel protocol stack packet loss, virtualization network packet software package compatibility, file query, and download, as well as open source software package risk detection services for developers, OSVs, and enterprises who are porting from CentOS and Fedora to0 码力 | 116 页 | 3.16 MB | 1 年前3 openEuler OS Technical Whitepaper
Innovation Projects
(June, 2023)interactions between the REE and TEE and big data interaction. secGear architecture Scenario Financial risk control Hardware security module alternative Fully-encrypted database with software and hardware System performance diagnosis: TCP and I/O performance jitter diagnosis in common scenarios. • System risk inspection: Second-level inspection on kernel protocol stack packet loss, virtualization network packet software package compatibility, file query, and download, as well as open source software package risk detection services for developers, OSVs, and enterprises who are porting from CentOS and Fedora to0 码力 | 116 页 | 3.16 MB | 1 年前3
 Kubernetes安全求生指南NIST在容器安全指南中揭露了五種容器應用最應關注的風險 映像風險 Image Risk 登錄風險 Registry Risk 容器調度平台風險 Orchestrator Risk 容器風險 Container Risk 實體作業系統風險 Host OS Risk ©2019 VMware, Inc. 9 針對Kubernetes的安全強化實作參考:0 码力 | 23 页 | 2.14 MB | 1 年前3 Kubernetes安全求生指南NIST在容器安全指南中揭露了五種容器應用最應關注的風險 映像風險 Image Risk 登錄風險 Registry Risk 容器調度平台風險 Orchestrator Risk 容器風險 Container Risk 實體作業系統風險 Host OS Risk ©2019 VMware, Inc. 9 針對Kubernetes的安全強化實作參考:0 码力 | 23 页 | 2.14 MB | 1 年前3
 Peering Forward: C++'s Next Decadesecrets, … Software safety (or “life safety” or similar) making software free from unacceptable risk of causing unintended harm to humans, property, or the environment examples: hospital equipment, simplification in Cpp2, because they let programmers declare their intent Because it carried the highest risk: Would the committee & community accept that huge a leap forward in compile-time programming? Would the language feature, not a divergent special-purpose extension” such as a different kind of loop Risk of bottom-up design is that we may end up with overlapping pieces that don’t fill in the whole picture0 码力 | 84 页 | 6.21 MB | 6 月前3 Peering Forward: C++'s Next Decadesecrets, … Software safety (or “life safety” or similar) making software free from unacceptable risk of causing unintended harm to humans, property, or the environment examples: hospital equipment, simplification in Cpp2, because they let programmers declare their intent Because it carried the highest risk: Would the committee & community accept that huge a leap forward in compile-time programming? Would the language feature, not a divergent special-purpose extension” such as a different kind of loop Risk of bottom-up design is that we may end up with overlapping pieces that don’t fill in the whole picture0 码力 | 84 页 | 6.21 MB | 6 月前3
 PostgreSQL 9.3.25 DocumentationTypes to numeric before dividing and back to money afterwards. (The latter is preferable to avoid risk- ing precision loss.) When a money value is divided by another money value, the result is double precision guaranteed in case of a crash of the database software; only abrupt operating system stoppage creates a risk of data loss or corruption when these settings are used. • Place the database cluster’s data directory synchronous_commit; there might be no need to write the WAL to disk on every commit. This setting does risk transaction loss (though not data corruption) in case of a crash of the database alone. 389 III0 码力 | 3002 页 | 7.47 MB | 1 年前3 PostgreSQL 9.3.25 DocumentationTypes to numeric before dividing and back to money afterwards. (The latter is preferable to avoid risk- ing precision loss.) When a money value is divided by another money value, the result is double precision guaranteed in case of a crash of the database software; only abrupt operating system stoppage creates a risk of data loss or corruption when these settings are used. • Place the database cluster’s data directory synchronous_commit; there might be no need to write the WAL to disk on every commit. This setting does risk transaction loss (though not data corruption) in case of a crash of the database alone. 389 III0 码力 | 3002 页 | 7.47 MB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100













