Difference between revisions of "Project Proposals/SRT"
(→Scope) |
(→Vendor Neutral) |
||
| Line 101: | Line 101: | ||
Please describe any such issues here. | Please describe any such issues here. | ||
--> | --> | ||
| + | |||
| + | No issue regarding vendor neutrality. | ||
== Meets Board Policy (including IPR, being within Board defined Scope etc) == | == Meets Board Policy (including IPR, being within Board defined Scope etc) == | ||
Revision as of 01:28, 23 July 2016
| srt Facts |
|
Project Lead:
Repository: git clone https://gerrit.fd.io/r/srt |
Contents
Name
Security Response Team
Project Contact Name and Email
Repository Name
srt
Description
Key security activities for this phase include:
•Conduct the risk assessment and use the results to supplement the base line security controls;
•Analyze security requirements;
•Perform functional and security testing;
•Prepare initial documents for system certification and accreditation; and
•Design security architecture.
Although this section presents the information security components in a sequential top-down manner, the order of completion is not necessarily fixed. Security analysis of complex systems will need to be iterated until consistency and completeness is achieved.
Scope
Initial Committers
Vendor Neutral
No issue regarding vendor neutrality.
Meets Board Policy (including IPR, being within Board defined Scope etc)
Meets board policy as expressed in Technical Community Charter and IP Policy
Administrata
- Request for Project proposal consideration
- Email: (place link to email to TSC proposing project, this can be obtained from TSC Archives
- Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on)
