Some advice about "high security", when to deploy a new security measure/strategy/product, and security product skepticism from the Vulnerability Assessment Team at Argonne National Laboratory.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online from Scribd
Some advice about "high security", when to deploy a new security measure/strategy/product, and security product skepticism from the Vulnerability Assessment Team at Argonne National Laboratory.
Some advice about "high security", when to deploy a new security measure/strategy/product, and security product skepticism from the Vulnerability Assessment Team at Argonne National Laboratory.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online from Scribd
Some advice about "high security", when to deploy a new security measure/strategy/product, and security product skepticism from the Vulnerability Assessment Team at Argonne National Laboratory.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 1
High Security is not a product attribute. Its a value judgment.
-- Roger Johnston, Argonne Vulnerability Assessment Team
In contemplating the use of any new security measure, strategy, or product, you need to determine the correct answers to 3 questions: (1) To what extend does this really improve security? (2) What are all the costs, tradeoffs, and side effects (because there always are some)? (3) Is 1 commensurate with 2? -- Roger Johnston, Argonne Vulnerability Assessment Team
For more about the VAT and security in general: http://www.ne.anl.gov/capabilities/vat
