Enterprise Security
Identity Theft Prevention Program Proposal PDF Print E-mail
Security - Enterprise Security
Monday, 16 March 2009 00:00

 

The following is a mock memo to the CEO of a credit card company. This letter provides a high level overview of the Red Flags rule (see references for background information) and is meant to gain executive management's support in implementing the regulated requirements for complaince with the FACT 2003 Law.

 

Identity Theft and Compliance with Red Flags Rule Requirements

This memo addresses concerns and requirements related to the Red Flags Rule, which is a component of the “Fair and Accurate Credit Transactions Act of 2003” (FACT 2003). As a creditor organization, we are required to meet certain requirements outlined in sections 114 and elsewhere in the FACT 2003 law. In order to comply with this rule we are required to implement a set of policies and procedures in order to prevent, detect, and mitigate identity theft and data breaches related to our customers’ private and personal information. The FTC originally set a deadline for compliance of November 1, 2008; however, this date has been extended to May 1, 2009. Therefore, it is crucial that we rapidly develop and implement our identity theft prevent program before this date.

Click here to read the full article...
 
Fair Information Practices: Overview and Application to the Omnibus Approach (Presentation) PDF Print E-mail
Security - Enterprise Security
Thursday, 26 February 2009 00:00

 

The following presentation is designed to give an overview on the Fair Information Practices. This presentation was originally used in a class project on the creation of an Omnibus Privacy Law in the United States. The Fair Information Practices were originally developed in the United States, but were not actively enacted through laws and regulations there. However, the concepts took hold in the European Union. You can get an overview on the Fair Information Practices here. This presentation was designed to be presented at a congressional hearing in order to help bring the members of congress upto speed on the topic.

 

 

 
Fair Information Practices: Implementing In Businesses (Presentation) PDF Print E-mail
Security - Enterprise Security
Thursday, 26 February 2009 00:00

 

The following presentation was originally part of a class project on the Fair Information Practices.The presentation is designed for companies and other organizations in the private sector to better understand how the passage of an Omnibus Privacy Law would affect their busienss operations and processes. The presentation provides the highlights of action which must be taken to comply with privacy guidelines.

 

 

 

 
Fair Information Practices For System Developers PDF Print E-mail
Security - Enterprise Security
Thursday, 26 February 2009 00:00

 

This is the last in a series of three presentations on the Fair Information Practices. This presentation is designed for system developers who create information managment and network systems. If an omnibus privacy law was passed, then busiensses would fall under new requirements. In order to remain competitive, vendors would have to update their products in order to facilitate compliance. Therefore, this presentation explains the types of changes that would need to be implemented in various systems and software in order to meet the privacy guidelines of the FIPs.

 

 

 

 
Building Security into System Design PDF Print E-mail
Security - Enterprise Security
Thursday, 05 February 2009 10:56

Summary

In this article [1], Hale argues that information systems need to be designed with security as a primary factor. He starts the article be emphasizing the number of attacks and their related costs. He notes it is relatively inexpensive to hack any given enterprise which is specifically targeted by skilled hackers, who are always a step ahead of the security researchers and patch writers. He notes that in general, systems are not designed with security in mind, and as a result, security holes and backdoors are only discovered after deployment. As a result, an organization is always playing catch-up to the hackers. If systems are designed to not only function well, but with the goal of increasing security less attacks will be possible. The article notes that security does not just magically appear, but that is must be explicitly addressed and built in to any given system. When a system is purchased or built internally security cannot be an afterthought. Hale concludes by recognizing it is impossible to make any system 100% secure, but that a security centric system stands a better chance of resisting attack. A weak system is not going to be secured by an additional security measure such as a firewall. 

Relation to Enterprise Security

The security team within an enterprise often focuses on discovering and patching security vulnerabilities. While this is often one of the top tasks for the team, it would be better if more time was spent proactively thinking about security. When products are purchased from outside vendors, they should be analyzed and reviewed for their security characteristics. This process would include reviewing NIST/CERT and other reports for the application. Other possibilities include reading product reviews written by security professionals and organizations as opposed to white paper or general commercial reviews. When products are developed internally, it is important to have a quality assurance team which is well versed in secure coding procedures and practices. In addition, the application should be tested with security tools in a sandbox before deployment. By doing the upfront analysis, the costs of later mitigation are reduced because many of the obvious and easily identifiable security vulnerabilities have been eliminated. 

When security is an afterthought, the security team will always be playing catch up to the attackers. As a result, the attacks will be more costly because of time limitations based upon the urgency and criticality of the vulnerability. In addition, the proactive approach will help create security consciousness within the enterprise which will help in anticipating and reacting to the inevitable attacks. 

Discussion

I believe encouraging vendor security consciousness would also be a valuable presentation. I believe that even if this increased the costs of the software or information system, customers would be willing to pay more upfront for a more secure system. Customers could take the word of the vendor; however, it would be more useful if there was some trusted organization which could provide a score on the security or evaluate the security evaluations used internally by the vendor. 

I am sure that every day, many security professional make earn their salary finding the same common vulnerabilities over and over again on their customer’s systems. While this is great for the auditors and penetration testers, it is a waste for the customer. The customer organization could have saved more money up front making security conscious decisions. In addition, this would then allow the penetration testers and security researchers to focus on more intricate and complex vulnerabilities, instead of focusing on the simple exploits that can often be perpetrated with a found script or with “script kiddie” tool kits.

While it is not desirable, it is understandable that many companies continue to use vulnerable software and systems which are known to be insecure. At the time of the initial investment many years ago, security was probably not a hot topic or a major concern. Now, they are stuck with these systems until then next purchasing or upgrade cycle. I believe that today security has become more prominent, and that vendors will work to make their products much more secure. This is not only because of increased awareness, but the new reality of negative publicity and diminished customer retention that can result from being flagged as a vendor of insecure or “easily hacked” products. 
 
 

References

1. Hale, Gregory. Think Network Security First, System Second. Enterprise Security Today. [Online] NewsFactor Network, February 4, 2009. [Cited: February 5, 2009.] http://www.enterprise-security-today.com/story.xhtml?story_id=0110018EEM4R.


 
<< Start < Prev 1 2 3 Next > End >>

Page 1 of 3