本文旨在将21434中各阶段涉及的WP统一梳理出来，方便学习及查阅。
“WP” for a work product | |||
序号 | 编号 | 标准原文 | 中文翻译 |
| 1 | WP-05-01 | Cybersecurity policy, rules and processes, resulting from the requirements of 5.4.1 to 5.4.3 | 网络安全政策、规则和流程，来自5.4.1至5.4.3的结果 |
| 2 | WP-05-02 | Evidence of competence management, awareness management resulting from [RQ-05-07] and continuous improvement resulting from [RQ-05-08] of 5.4.2 | 能力管理的证据，来自5.4.2的[RQ-05-07]意识管理的结果和由[RQ-05-08]持续改进的结果 |
| 3 | WP-05-03 | Evidence of the organization's management systems, resulting from the requirements of 5.4.4 and 5.4.6 | 组织管理体系的证明，来自5.4.4和5.4.6的结果 |
| 4 | WP-05-04 | Evidence of tool management, resulting from the requirements of 5.4.5 | 工具管理的证明，来自5.4.5的结果 |
| 5 | WP-05-05 | Organizational cybersecurity audit report, resulting from the requirements of 5.4.7 | 组织网络安全审计报告，来自5.4.7的结果 |
| 6 | WP-06-01 | Cybersecurity plan, resulting from the requirements of 6.4.1 to 6.4.6 | 网络安全计划，来自6.4.1至6.4.6的结果 |
| 7 | WP-06-02 | Cybersecurity case, resulting from the requirements of 6.4.7 | 网络安全案例，来自6.4.7的结果 |
| 8 | WP-06-03 | Cybersecurity assessment report, if applicable, resulting from the requirements of 6.4.8 | 网络安全评估报告（如适用），来自6.4.8的结果 |
| 9 | WP-06-04 | Release for post-development report, resulting from the requirements of 6.4.9 | 发布开发后报告，来自6.4.9的结果 |
| 10 | WP-07-01 | Cybersecurity interface agreement, resulting from the requirements of 7.4.3 | 网络安全接口协议，来自7.4.3的结果 |
| 11 | WP-08-01 | Sources for cybersecurity information, resulting from [RQ-08-01] | 网络安全信息来源，来自[RQ-08-01]的结果 |
| 12 | WP-08-02 | Triggers, resulting from [RQ-08-02] | 触发器，来自[RQ-08-02]的结果 |
| 13 | WP-08-03 | Cybersecurity events, resulting from [RQ-08-03] | 网络安全事件，来自[RQ-08-03]的结果 |
| 14 | WP-08-04 | Weaknesses from cybersecurity events, resulting from [RQ-08-04] | 网络安全事件的弱点，来自[RQ-08-04]的结果 |
| 15 | WP-08-05 | Vulnerability analysis, resulting from [RQ-08-05] and [RQ-08-06] | 脆弱性分析，来自 [RQ-08-05] 和 [RQ-08-06]的结果 |
| 16 | WP-08-06 | Evidence of managed vulnerabilities, resulting from [RQ-08-07] | 漏洞管理的证明，来自[RQ-08-07]的结果 |
| 17 | WP-09-01 | Item definition, resulting from the requirements of 9.3.2 | 相关项的定义,来自9.3.2要求的结果 |
| 18 | WP-09-02 | TARA, resulting from [RQ-09-03] and [RQ-09-04] | TARA，来自 [RQ-09-03] 和 [RQ-09-04]的结果 |
| 19 | WP-09-03 | Cybersecurity goals, resulting from [RQ-09-05] | 网络安全目标，来自 [RQ-09-05]的结果 |
| 20 | WP-09-04 | Cybersecurity claims, resulting from [RQ-09-06] | 网络安全声明，来自[RQ-09-06]的结果 |
| 21 | WP-09-05 | Verification report for cybersecurity goals, resulting from [RQ-09-07] | 网络安全目标验证报告，来自[RQ-09-07]的结果 |
| 22 | WP-09-06 | Cybersecurity concept, resulting from [RQ-09-08], [RQ-09-09] and [RQ-09-10] | 网络安全概念，来自[RQ-09-08], [RQ-09-09] 和 [RQ-09-10]的结果 |
| 23 | WP-09-07 | Verification report for the cybersecurity concept, resulting from [RQ-09-11] | 网络安全概念验证报告，来自[RQ-09-11]的结果 |
| 24 | WP-10-01 | Cybersecurity specifications, resulting from [RQ-10-01] and [RQ-10-02] | 网络安全规范，来自[RQ-10-01] 和 [RQ-10-02]的结果 |
| 25 | WP-10-02 | Cybersecurity requirements for post-development, resulting from [RQ-10-03] | 开发后的网络安全要求，来自[RQ-10-03]的结果 |
| 26 | WP-10-03 | Documentation of the modelling, design or programming languages and coding guidelines, if applicable, resulting from [RQ-10-04] and [RQ-10-05] | 有关建模、设计或编程语言及编码指引的文件（如适用），来自 [RQ-10-04] 和 [RQ-10-05]的结果 |
| 27 | WP-10-04 | Verification report for the cybersecurity specifications, resulting from [RQ-10-08] | 网络安全规范的验证报告，来自 [RQ-10-08]的结果 |
| 28 | WP-10-05 | Weaknesses found during product development, resulting from [RQ-10-07] and [RC-10-12], if applicable | 产品开发过程中发现的弱点（如适用），来自 [RQ-10-07] 和 [RC-10-12]的结果 |
| 29 | WP-10-06 | Integration and verification specification, resulting from [RQ-10-10] | 集成与验证规范，来自[RQ-10-10]的结果 |
| 30 | WP-10-07 | Integration and verification report, resulting from [RQ-10-09], [RQ-10-11] and [RC-10-12] | 集成与验证报告，来自[RQ-10-09], [RQ-10-11] 和 [RC-10-12]的结果 |
| 31 | WP-11-01 | Validation report, resulting from [RQ-11-01] and [RQ-11-02] | 验证报告，来自[RQ-11-01] 和 [RQ-11-02]的结果 |
| 32 | WP-12-01 | Production control plan, resulting from [RQ-12-01] and [RQ-12-02] | 生产控制计划，来自[RQ-12-01] 和 [RQ-12-02]的结果 |
| 33 | WP-13-01 | Cybersecurity incident response plan, resulting from [RQ-13-01] | 网络安全事件响应计划，来自 [RQ-13-01]的结果 |
| 34 | WP-14-01 | Procedures to communicate the end of cybersecurity support, resulting from [RQ-14-01] | 网络安全支持的沟通程序，来自 [RQ-14-01]的结果 |
| 35 | WP-15-01 | Damage scenarios, resulting from [RQ-15-01] | 损坏场景，来自[RQ-15-01]的结果 |
| 36 | WP-15-02 | Assets with cybersecurity properties, resulting from [RQ-15-02] | 具有网络安全属性的资产，来自 [RQ-15-02]的结果 |
| 37 | WP-15-03 | Threat scenarios, resulting from [RQ-15-03] | 威胁场景，来自[RQ-15-03]的结果 |
| 38 | WP-15-04 | Impact ratings with associated impact categories, resulting from [RQ-15-04] to [RQ-15-06] | 与影响类别相关的影响评级，来自[RQ-15-04] -- [RQ-15-06]的结果 |
| 39 | WP-15-05 | Attack paths, resulting from [RQ-15-08] and [RQ-15-09] | 攻击路径，来自[RQ-15-08] 和 [RQ-15-09]的结果 |
| 40 | WP-15-06 | Attack feasibility ratings, resulting from [RQ-15-10] | 攻击可能性评价，来自[RQ-15-10]的结果 |
| 41 | WP-15-07 | Risk values, resulting from [RQ-15-15] and [RQ-15-16] | 风险值，来自 [RQ-15-15] 和 [RQ-15-16]的结果 |
| 42 | WP-15-08 | Risk treatment decisions, resulting from [RQ-15-17] | 风险处置决策，来自 [RQ-15-17]的结果 |
我在从html页面生成PDF时遇到问题。我正在使用PDFkit。在安装它的过程中，我注意到我需要wkhtmltopdf。所以我也安装了它。我做了PDFkit的文档所说的一切......现在我在尝试加载PDF时遇到了这个错误。这里是错误:commandfailed:"/usr/local/bin/wkhtmltopdf""--margin-right""0.75in""--page-size""Letter""--margin-top""0.75in""--margin-bottom""0.75in""--encoding""UTF-8""--margin-left""0.75in""-
我在我的项目目录中完成了compasscreate.和compassinitrails。几个问题:我已将我的.sass文件放在public/stylesheets中。这是放置它们的正确位置吗？当我运行compasswatch时，它不会自动编译这些.sass文件。我必须手动指定文件:compasswatchpublic/stylesheets/myfile.sass等。如何让它自动运行？文件ie.css、print.css和screen.css已放在stylesheets/compiled。如何在编译后不让它们重新出现的情况下删除它们？我自己编译的.sass文件编译成compiled/t
我花了三天的时间用头撞墙，试图弄清楚为什么简单的“rake”不能通过我的规范文件。如果您遇到这种情况:任何文件夹路径中都不要有空格!。严重地。事实上，从现在开始，您命名的任何内容都没有空格。这是我的控制台输出:(在/Users/*****/Desktop/LearningRuby/learn_ruby)$rake/Users/*******/Desktop/LearningRuby/learn_ruby/00_hello/hello_spec.rb:116:in`require':cannotloadsuchfile--hello(LoadError) 最佳
关闭。这个问题需要detailsorclarity.它目前不接受答案。想改进这个问题吗？通过editingthispost添加细节并澄清问题.关闭8年前。Improvethisquestion在首页我有:汽车:VolvoSaabMercedesAudistatic_pages_spec.rb中的测试代码:it"shouldhavetherightselect"dovisithome_pathit{shouldhave_select('cars',:options=>['volvo','saab','mercedes','audi'])}end响应是rspec./spec/request
在Rails4.0.2中，我使用s3_direct_upload和aws-sdkgems直接为s3存储桶上传文件。在开发环境中它工作正常，但在生产环境中它会抛出如下错误，ActionView::Template::Error(noimplicitconversionofnilintoString)在View中，create_cv_url,:id=>"s3_uploader",:key=>"cv_uploads/{unique_id}/${filename}",:key_starts_with=>"cv_uploads/",:callback_param=>"cv[direct_uplo
使用Ruby1.9.2运行IDE提示说需要gemruby-debug-base19x并提供安装它。但是，在尝试安装它时会显示消息Failedtoinstallgems.Followinggemswerenotinstalled:C:/ProgramFiles(x86)/JetBrains/RubyMine3.2.4/rb/gems/ruby-debug-base19x-0.11.30.pre2.gem:Errorinstallingruby-debug-base19x-0.11.30.pre2.gem:The'linecache19'nativegemrequiresinstall
我知道全局变量$!包含最新的异常对象，但我对下面的语法感到困惑。谁能帮助我理解以下语法？rescue$! 最佳答案 此构造可防止异常停止您的程序并使堆栈跟踪冒泡。它还会将该异常作为值返回，这很有用。a=get_me_datarescue$!在此行之后，a将保存请求的数据或异常。然后您可以分析该异常并采取相应措施。defget_me_dataraise'Nodataforyou'enda=get_me_datarescue$!puts"Executioncarrieson"pa#>>Executioncarrieson#>>#更现实的
注意：本文主要掌握DCN自研无线产品的基本配置方法和注意事项，能够进行一般的项目实施、调试与运维AP基本配置命令AP登录用户名和密码均为：adminAP默认IP地址为：192.168.1.10AP默认情况下DHCP开启AP静态地址配置：setmanagementstatic-ip192.168.10.1AP开启/关闭DHCP功能：setmanagementdhcp-statusup/downAP设置默认网关：setstatic-ip-routegeteway192.168.10.254查看AP基本信息：getsystemgetmanagementgetmanaged-apgetrouteAP配
基础版云数据库RDS的产品系列包括基础版、高可用版、集群版、三节点企业版，本文介绍基础版实例的相关信息。RDS基础版实例也称为单机版实例，只有单个数据库节点，计算与存储分离，性价比超高。说明RDS基础版实例只有一个数据库节点，没有备节点作为热备份，因此当该节点意外宕机或者执行重启实例、变更配置、版本升级等任务时，会出现较长时间的不可用。如果业务对数据库的可用性要求较高，不建议使用基础版实例，可选择其他系列（如高可用版），部分基础版实例也支持升级为高可用版。基础版与高可用版的对比拓扑图如下所示。优势 性能由于不提供备节点，主节点不会因为实时的数据库复制而产生额外的性能开销，因此基础版的性能相对于
我在我正在处理的一些代码中发现了这一点。它旨在解决从磁盘读取key文件的要求。在生产环境中，key文件的内容位于环境变量中。旧代码:key=File.read('path/to/key.pem')新代码:key=File.read('|echo$KEY_VARIABLE')这是如何工作的？ 最佳答案 来自IOdocs:Astringstartingwith“|”indicatesasubprocess.Theremainderofthestringfollowingthe“|”isinvokedasaprocesswithappro
