Security engineering

Security engineering is a specialized field of engineering that focuses on the security aspects in the design of systems that need to be able to deal robustly with possible sources of disruption, ranging from natural disasters to malicious acts. It is similar to other systems engineering activities in that its primary motivation is to support the delivery of engineering solutions that satisfy pre-defined functional and user requirements, but with the added dimension of preventing misuse and malicious behavior. These constraints and restrictions are often asserted as a security policy.

In one form or another, security engineering has existed as an informal field of study for several centuries. For example, the fields of locksmithing and security printing have been around for many years.

Due to recent catastrophic events, most notably 9/11, Security Engineering has quickly become a rapidly growing field. In fact, in a recent report completed in 2006, it was estimated that the global security industry was valued at US$150 billion.

Security engineering involves aspects of social science, psychology (such as designing a system to 'fail well' instead of trying to eliminate all sources of error) and economics, as well as physics, chemistry, mathematics, architecture and landscaping.^[1] Some of the techniques used, such as fault tree analysis, are derived from safety engineering.

Other techniques such as cryptography were previously restricted to military applications. One of the pioneers of security engineering as a formal field of study is Ross Anderson.

Qualifications

No single qualification exists to become a security engineer.

However, an undergraduate and/or graduate degree, often in computer science, computer engineering, or information assurance, in combination with practical work experience (systems, network engineering, software development, etc.) most qualifies an individual to succeed in the field. Multiple certifications, such as the Certified Information Systems Security Professional, are available that may demonstrate expertise in the field.

Security stance

The two possible default positions on security matters are:

• Default deny - everything not explicitly permitted is forbidden

Improves security at a cost in functionality.

This is a good approach if you have lots of security threats.

• Default permit - everything not explicitly forbidden is permitted

Allows greater functionality by sacrificing security.

This is only a good approach in an environment where security threats are non-existent or negligible.

See computer insecurity for an example of the failure of this approach in the real world.

Core practices

• Security Requirements Analysis
• Secure coding
• Security testing
• Engineering Product Lifecycle
• Economics of security

Sub-fields

• Information security

• protecting data from unauthorized access, use, disclosure, destruction, modification, or disruption to access.
• See esp. Computer security

• Physical security

• deter attackers from accessing a facility, resource, or information stored on physical media.

• Technical surveillance counter-measures
• Economics of security

• the economic aspects of economics of privacy and computer security.

Methodologies

Technological advances, principally in the field of computers, have now allowed the creation of far more complex systems, with new and complex security problems. Because modern systems cut across many areas of human endeavor, security engineers not only need consider the mathematical and physical properties of systems; they also need to consider attacks on the people who use and form parts of those systems using social engineering attacks. Secure systems have to resist not only technical attacks, but also coercion, fraud, and deception by confidence tricksters.

Web applications

According to the Microsoft Developer Network the patterns and practices of security engineering consist of the following activities:^[2]

• Security Objectives
• Security Design Guidelines
• Security Modeling
• Security Architecture and Design Review
• Security Code Review
• Security Testing
• Security Tuning
• Security Deployment Review

These activities are designed to help meet security objectives in the software life cycle.

Physical

Canadian Embassy in Washington, D.C. showing planters being used as vehicle barriers, and barriers and gates along the vehicle entrance

• Understanding of a typical threat and the usual risks to people and property.
• Understanding the incentives created both by the threat and the countermeasures.
• Understanding risk and threat analysis methodology and the benefits of an empirical study of the physical security of a facility.
• Understanding how to apply the methodology to buildings, critical infrastructure, ports, public transport and other facilities/compounds.
• Overview of common physical and technological methods of protection and understanding their roles in deterrence, detection and mitigation.
• Determining and prioritizing security needs and aligning them with the perceived threats and the available budget.

Target hardening

Whatever the target, there are multiple ways of preventing penetration by unwanted or unauthorised persons. Methods include placing Jersey barriers, stairs or other sturdy obstacles outside tall or politically sensitive buildings to prevent car and truck bombings. Improving the method of visitor management and some new electronic locks take advantage of technologies such as fingerprint scanning, iris or retinal scanning, and voiceprint identification to authenticate users.

Employers of security engineers

• US Department of State, Bureau of Diplomatic Security (ABET certified institution degree in engineering or physics required)^[3]
• Security Engineering Sal, ^[4]
• Google^[5]
• Financial Services Industry, Health Care Industry,^[6] Energy Sector^[7]

See also

References

Further reading

• Ross Anderson (2001). Security Engineering. Wiley. ISBN 0-471-38922-6. 
• Ross Anderson (2008). Security Engineering - A Guide to Building Dependable Distributed Systems. Wiley. ISBN 0-470-06852-3. 
• Ross Anderson (2001). "Why Information Security is Hard - An Economic Perspective"
• Bruce Schneier (1995). Applied Cryptography (2nd ed.). Wiley. ISBN 0-471-11709-9. 
• Bruce Schneier (2000). Secrets and Lies: Digital Security in a Networked World. Wiley. ISBN 0-471-25311-1. 
• David A. Wheeler (2003). "Secure Programming for Linux and Unix HOWTO". Linux Documentation Project. Retrieved 2005-12-19. 
• Ron Ross, Michael McEvilley, Janet Carrier Oren (2016). "Systems Security Engineering" (PDF). Internet of Things. Retrieved 2016-11-22. CS1 maint: Multiple names: authors list (link)

Articles and papers

• patterns & practices Security Engineering on Channel9
• patterns & practices Security Engineering on MSDN
• patterns & practices Security Engineering Explained
• Basic Target Hardening from the Government of South Australia