Author: bh
Date: 2007-10-18 16:32:14 +0200 (Thu, 18 Oct 2007)
New Revision: 451
Modified:
trunk/doc/website/creation-process-nvt.htm4
Log:
Fix some typos
Modified: trunk/doc/website/creation-process-nvt.htm4
===================================================================
--- trunk/doc/website/creation-process-nvt.htm4 2007-10-18 14:23:45 UTC (rev
450)
+++ trunk/doc/website/creation-process-nvt.htm4 2007-10-18 14:32:14 UTC (rev
451)
@@ -42,7 +42,7 @@
<p>
This document describes the creation process for Network Vulnerability Tests
(NVTs)
for the network security scanner OpenVAS.
-NVTs are test routines that check for presence of a vulerability at a target
system.
+NVTs are test routines that check for presence of a vulnerability at a target
system.
OpenVAS coordinates the execution of many of such tests to many target systems
and collects the results.
</p>
@@ -54,11 +54,11 @@
<p>
The most important phases of this process are: Initial priorisation
(Evaluation),
-final priorisation (Decision), implementation, Quality assurance und
release/distribution.
+final priorisation (Decision), implementation, Quality assurance and
release/distribution.
</p>
<p>
-These phases as well as supporting technolgies are described in more detail
below.
+These phases as well as supporting technologies are described in more detail
below.
</p>
<h3>Short summary</h3>
@@ -73,7 +73,7 @@
<p>
The used sources of security advisories are carefully selected
and connected with a automatic notification process.
-Thus, the intial priorisation is an ongoing process driven by
+Thus, the initial priorisation is an ongoing process driven by
such notifications.
</p>
@@ -93,23 +93,23 @@
<ul>
<li>Evaluation: The evaluation team, alerted by a security advisory
notification,
- applies the evaluation matrix and thus comes to the intial priorisation.
+ applies the evaluation matrix and thus comes to the initial priorisation.
This information is added to the general priority overview.
<li>Decision: The decision team selects those security alerts for which the
implementation
- of a corrsponding NVT is highly desired (final prioristation). This
decision making
+ of a corresponding NVT is highly desired (final priorisation). This
decision making
takes place according to a defined schedule.
<li>Implementation: The development team actually implements a NVT.
In case of problems (solution strategy unclear or effort very high)
the issue is handed back to the decision team for reconsideration.
-<li>Quality Assurance: The QS team executes the quality assurance for the
results
+<li>Quality Assurance: The QA team executes the quality assurance for the
results
of the development team. If a NVT does not meet the quality standard, the
issue is handed back to the development team.
<li>Release/Distribution: The release (transfer of new NWT into NWT
distribution mechanism)
- is the last step to be done by the QS team in case the NVT passes quality
tests.
+ is the last step to be done by the QA team in case the NVT passes quality
tests.
</ul>
_______________________________________________
Openvas-commits mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-commits
