Back to Results
First PageMeta Content
Crime prevention / National security / Computing / Software quality / Evaluation / Common Criteria / Software bug / Fuzz testing / Reliability engineering / Software testing / Security / Computer security


CHAPTER 26 System Evaluation and Assurance If it’s provably secure, it probably isn’t.
Add to Reading List

Document Date: 2011-12-05 05:56:48

Open Document

File Size: 391,25 KB

Share Result on Facebook

City

San Francisco / /

Company

IBM / Gary McGraw’s / TIS / Microsoft / Cisco / /

Country

United States / /

Currency

USD / /

Facility

Carnegie-Mellon University / Asian restaurant / Software Engineering Institute / /

IndustryTerm

bank inspection / line encryption devices / healthcare environment / cryptographic protocols / software vendors / software engineers / security printing technologies / concentrated / defense networks / cryptographic algorithms / Internet fall / banking / commodity operating systems / crypto protocols / mature product / food guides / /

NaturalFeature

Internet fall / /

OperatingSystem

Microsoft Windows / /

Organization

Software Engineering Institute / System Evaluation and Assurance Formal Methods In Chapter / Assurance Formal Methods In Chapter / Carnegie-Mellon University / /

Person

Greg Hoglund / Lars Knudsen / Hans van Vliet / Prince / David Litchfield / Eric Raymond / Janet Reno / Bruce Schneier / Joseph Schumpeter / /

Position

Prince / capable project manager / administrator / maintenance programmer / working engineer / Attorney General / head / waterfall model of system development / programmer / /

ProgrammingLanguage

SQL / /

Technology

encryption / cryptography / firewall / security printing technologies / mobile phones / operating systems / anti-virus software / key management protocols / /

SocialTag