datasheets.com EBN.com EDN.com EETimes.com Embedded.com PlanetAnalog.com TechOnline.com  
Events
UBM Tech
UBM Tech
Welcome Guest Log In | Register

Meeting Government Security Requirements: The Difference Between Selling to the Government and Not

Authored on: Apr 8, 2005

Technical Paper

0 0
More InfoLess Info
The government market has always been a lucrative market for technology companies. As government communications become more and more networked, the range of devices to access this network has grown, and with it, the need for security. Many of these devices require security and the government will be spending a lot of money to satisfy these requirements.

Federal Information Processing Standard (FIPS) 140-2 has become the de facto security standard within the government—not only in the United States, but in other countries as well. Other industries such as healthcare and finance have also adopted FIPS 140-2 because of the high degree of security it specifies. Under the US Federal Government's Crypto Modernization Program, requirements such as Elliptic Curve Cryptography are also making headway in the government space and will have greater impact in the future.

However, the road to FIPS Validation is long, complex and expensive, and the FIPS standards themselves require constant monitoring to ensure compliance. Vendors looking to capitalize on sales to the government need a solution that will simplify the process of getting to market for them and offer the flexibility to meet future requirements.



Please disable any pop-up blockers for proper viewing of this paper.

0 comments
write a comment

Please Login

You will be redirected to the login page

×

Please Login

You will be redirected to the login page

×

Please Login

You will be redirected to the login page