JavaScriptMessages
APEC
Asia Pacific Economic Cooperation
SiteMap
Login
Glossary
Filter:
#
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
All
Return to List
V
V Model
V7
Vaccines
Vadding
Valid Password
Valid period
Validation
Validation (Testing)
Value of protection
Value Of The Represented
Value-Added Networks
Vanilla
Vannevar
Vaporware
Var
Variable Length Buffer
Variant
VAX
VAXectomy
VAXen
Vaxherd
Vaxism
Vaxocentrism
VBscript
Vdiff
VDT
Veeblefester
Vendor diversity
Vendor Security Analyst
Ventilator Card
Venus Flytrap
Verbage
Verbiage
Verifiable Identification Forwarding
Verification
Verification And Validation Process
Verified Design
Verifier
Version 7
Vgrep
Vi
Victimization software
Video Display Terminal
Video Display Unit
Video recorder
Video Signal
Videotex
Videotext
View
Viewdata
Violation
Violations
Virgin
Virtual
Virtual Call
Virtual Call Capability
Virtual Call Facility
Virtual Carrier Frequency
Virtual Circuit
Virtual Circuit Capability
Virtual Connection
Virtual Friday
Virtual Memory
Virtual Network
Virtual Password
Virtual private network (VPN)
Virtual Reality
Virtual Shredder
Virtual Storage
Virus
Visionary
VMS
Vocoder
Voice
Voice Communications Security
Voice Mail Security
Voice recognition
Voice-Net
Volatile Memory
Volatility
Volume
Voluntary tunneling
Voodoo Programming
VPN (virtual private network)
VR
VSA
VST
VTT
Vulcan Nerve Pinch
Vulnerability
Vulnerability Analysis
Vulnerability Assessment
Vulnerability assessment tools
Vulnerability reporters
Vulnerability testing
Vulnerability testing contract
Vulture Capitalist
Verification
In authentication, used when a user claims to be a specific person; there is a one-to-one comparison between the applicant and a single profile in the authentication database. See Identification.
The documentation of penetration or attempts to penetrate an actual on-line system in support or in contradiction of assumptions developed during system review and analysis. (AR 380-380;) 2. The successful testing and documentation of actual on-line system penetration or attempts to penetrate the system in support or in contradiction or assumptions developed during system review and analysis which are to be included in the evaluation report. (DODD 5200. 28M;) 3. The process of comparing two levels of system specification for proper correspondence (e. g. , security policy model with top-level specifications, top-level specification with source code, or source code with object code). This process may or may not be automated. (NCSC-WA-001-85;; CSC-STD-001-83;)