November 1, 2011
Security Conference List – Wikipedia Rocks
Wikipedia truly is amazing. Check out the list of worldwide security conferences. This is a great place to look for any professionals wanting to speak or attend a high profile conferences. Definitely a good site to add to my links page.
October 30, 2011
Is Your 3rd Party Provider Secure?
Rogue Russian entities in the advertising industry take millions and the entire company disappears. Poor security programming techniques from offshore entities expose cross site scripting flaws in 50% of the companies websites. In any event more and more security weakness is exposed by the poor practices associated with a vendor, partner, or other third party business entity. These third party entities and the services they provide can cause great exposure resulting in large scale financial problems to the host organization.
What can be done?
Security of third party entities can be accomplished in many ways, but it has to start with the relationship and contracts in place. Once there is a contract then each practice can be broken down. Third party security assessments typically include two main practices. These are:
- Technical Security Testing
- Checklist Validation Assessments
Technical Security Testing usually involves network vulnerability scanning, penetration testing, application testing, and sometimes security configuration reviews. This approach occurs when a third party is contracted to assess the host organization. This is a third party assessment however this situation addresses contracting a third party to perform the assessment. The other focuses on assessing the host organizations third party service providers, not contracting a third party to perform an assessment.
Checklist validation assessments are commonly used for assessing ones service providers. One of the most common used tools for this practice is supplied online by Shared Assessments. The Shared assessments questionnaire and agreed upon procedures guides are used in many different countries around the world. They are very comprehensive and allow for customization if required. The core components that make this tool fantastic for third party risk assessments are:
- Excel based checklist format which can be auto compared against a configured baseline
- Comprehensive list of standard questions that map to some different compliance regulations
The Shared Assessments program has done a good job explaining the tool use and to avoid repeating the information that is clearly explained online the focus will be to explain leveraging the tool to build a third party assessment function in the organization. Building the third party assessment requires some dedicated resource time for the following responsibilities.
- Determining the assessment schedule and prioritization
- Customizing the questionnaires
- Phone and email follow up to third parties
- Onsite review and validation (if applicable based on the assessment type)
- Providing reports to management and third party entities
- Follow up on remediation efforts
Shared Assessments – Useful
Back in 2009 my blog entry was titled “BITS Shared Assessments – Useful or Not”. After several more years and reviewing hundreds of clients it appears this is now the predominantly used assessment practice. Organizations have used the main content and questions then customized and integrated them into formal programs. I still find the validation component one of the weakest links, but in some cases that also falls on the assessor. To help mitigate the risk organizations should be looking at some kind of technical and checklist testing of their entities. Using both of these will help make up for deficiencies in the checklist based approaches.
I encourage others to comment if they have seen different standards for third party assessment especially those around the checklist and validation approach. As today the Shared Assessments appears to still be the number one choice implemented and used based on my experience with other companies.
August 24, 2010
Penetration Testing Risks
What are the risks to someone performing a penetration test?
It seems this question has been asked a 100 times yet the other day I was typing up the same answers again because for some reason there was no write up.
This is generic, but hopefully it saves us all time in the future.
Risks:
Basically there are two key risks.
- There is no guarantee systems won’t have some type of denial of service.
This is typically a result of having older legacy systems or custom applications, which are taken offline by an automated vulnerability scanner or over abuse by the attacker.
2. Bandwidth or system utilization may be increased thus resulting in performance loss.
Based on the amount of the automated scanning, the size of the network pipes (both scanning and target), and the number of open ports on a particular system it is possible to overwhelm a service or medium resulting in a performance loss.
Mitigating Risks:
To help prevent a denial of service many approaches can be taken. Here are some examples.
1. Exclude legacy systems from automated testing. To ensure security perform manual testing of excluded items.
2. Exclude custom applications from automated testing. To ensure security perform manual testing of excluded applications.
3. Perform testing of critical systems during off hours. Critical systems can be scheduled for testing during low volume business or off business hours.
4. Perform testing in a phased manner starting with user acceptance testing (UAT) environments to ensure the actual tests do not affect particular systems or networks. Once UAT is complete then begin testing on production environments.
5. Setup monitoring and escalation procedures prior to testing. Ensure fault management is in place to ensure systems send alerts when they go down. Ensure proper phone numbers and other contact information is defined to immediately investigate and restore services in the event of a problem. Escalation procedures should include contact information for the person performing the testing to immediately stop all testing if required.
To help prevent bandwidth issues automated testing can be throttled back to use less bandwidth. Also the number of ports can be reduced if there is a concern for overloading a particular group of systems. Usually it is recommended to test the UAT environment instead of reducing the number of ports because certain vulnerabilities may be missed.
December 7, 2007
Test Your Anti-Virus or Re-Install
On strategic risk assessments not testing the anti-virus signatures before being deployed should be considered a vulnerability. Many of my customers believe this is ridiculous and not practical, however I report it anyway. Whatever the case, the organization has the decision to accept the risk, as I am only there to point it out. There is a great example published where a routine update caused serious problems forcing customers to have to re-install the operating system.
http://news.yahoo.com/s/zd/20071206/tc_zd/221141;_ylt=AhIN_X.SMrgYGlzdK7zmNe8E1vAI
So you decide. Should Anti-virus software be tested before deployment.
November 13, 2007
Malware Embedded in Advertising – What is the Solution?
Malware is everywhere and becoming one of the most common security threats in the industry. The link below provides some insight into the seriousness of this issue.
There really is not a great solution for this problem at this time, but how can a company that serves adds mitigate the risk. There are several ways.
-
Ensure all ads that are uploaded are hashed in some way to ensure the add being delivered is the add uploaded by the client.
-
Use file monitoring tools like tripwire on image servers to help ensure that adds are not modified. This will also help provide proof if there is an actual attack on the add server.
-
Scan adds with anti-virus software. Although this will not catch everything it will catch some of the files.
-
Scan adds for known malware URL’s to prevent phishing type attacks. (This is like a signature based solution and takes a great deal of maintenance to keep up with the attackers)
-
Hope someone comes up with a good solution that can regularly scan all the adds for malware.
The above will help limit the liability of the ad company serving adds and has some preventive measures that can be implemented to protect both the add companies brand and their customers who may be uploading malware adds without knowing it.
November 8, 2007
IP Address BlackList
IP Address Blacklists are great for short time security events. This information is important for a paper that I am working. It took me a while to find this information again. I actually had to dig into an old email file to get all of the information because typical internet search engines were not providing good results.
Here is a good list of IP addresses and ranges that can be blacklisted to help prevent DOS attacks, etc. Before using this list be sure your organization does not have clients in the below ranges.
Dshield Top 10 Attack IP’s
http://www.dshield.org/top10.php
- 074.052.180.114
- 218.003.209.174
- 211.106.172.081
- 195.068.089.211
- 121.015.253.104
- 218.004.137.213
- 202.062.224.090
- 150.164.029.253
- 058.215.065.237
- 218.006.009.099
Dshield Recommend Block List
http://feeds.dshield.org/block.txt
| Start | End | Country |
| 121.150.29.0 | 121.150.29.255 | |
| 64.80.28.0 | 64.80.28.255 | |
| 81.3.254.0 | 81.3.254.255 | |
| 139.55.62.0 | 139.55.62.255 | US |
| 139.55.82.0 | 139.55.82.255 | US |
| 203.152.123.0 | 203.152.123.255 | NZ |
| 196.22.194.0 | 196.22.194.255 | ZA |
| 139.55.113.0 | 139.55.113.255 | US |
| 81.3.248.0 | 81.3.248.255 | |
| 202.144.113.0 | 202.144.113.255 | IN |
| 139.55.97.0 | 139.55.97.255 | US |
| 121.18.13.0 | 121.18.13.255 | |
| 81.3.250.0 | 81.3.250.255 | |
| 121.18.12.0 | 121.18.12.255 | |
| 139.55.103.0 | 139.55.103.255 | US |
| 74.86.127.0 | 74.86.127.255 | |
| 200.207.155.0 | 200.207.155.255 | BR |
| 206.51.136.0 | 206.51.136.255 | CA |
| 85.88.191.0 | 85.88.191.255 | |
| 217.175.179.0 | 217.175.179.255 |
Asia Pacific Black List
http://www.apnic.net/db/ranges.html#country
- 58.0.0.0/8
- 59.0.0.0/8
- 60.0.0.0/8
- 61.0.0.0/8
- 116.0.0.0/8
- 117.0.0.0/8
- 118.0.0.0/8
- 119.0.0.0/8
- 120.0.0.0/8
- 121.0.0.0/8
- 122.0.0.0/8
- 123.0.0.0/8
- 124.0.0.0/8
- 125.0.0.0/8
- 126.0.0.0/8
- 169.208.0.0/12
- 202.0.0.0/8
- 203.0.0.0/8
- 210.0.0.0/8
- 211.0.0.0/8
- 218.0.0.0/8
- 219.0.0.0/8
- 220.0.0.0/8
- 221.0.0.0/8
- 222.0.0.0/8