paraDisE beyond the eArTH: December 2012

Thursday, 13 December 2012

Downtime Calculation

Downtime Calculation: Ex. A site which has only 2 hours downtime in a 30-days month will have downtime % like the following :-

D = Total downtime (in minutes)

T = Total time in the month (in minutes)

Downtime (in %) = D/T X 100

D = 2 X 60 minutes = 120 minutes

T = 30 days X 24 hours X 60 minutes = 43200 minutes

Downtime (in %)

= [120/43200] X 100

= 0.2777 %

Uptime (in %)

= 100 - 0.2777

= 99.7222 %

In other words, you have 99.722% of uptime throughout the month.

SLA % - usually calculated at 99.90%

Outage SLA (mins.) - 167 mins. in a year

Calculation Ex:

From 01-01-2012 to 31-12-2012 Holidays:8holidays+Fri+Sat off days adds upto 112 days holidays. So difference from day 1 of year until last day of year minus holidays = say 112 days

So total working days = 365 - 112 days = 253 working days. You may also calculate with excel formula; NETWORKDAYS.

So, Total number of minutes in working days = 253x11*60=166980

where 11 is the total business hours (may vary from organisation to org'n) in a day and 60 is for 1 hr.

So, 166980-(166980x99.90%) = 166.98 mins. Outage SLA in mins in a year for an org'n. should be around 167mins. Any downtime exceeding beyond 167 mins violates the SLA.

Monday, 3 December 2012

Important Vulnerability Basics

Use the vulnerability assessment tools to identify the vulnerabilities you need to repair. This will help protect your website or network against security breaches.

Vulnerabilities
Critical versus informational
Vulnerability assessment
Best practices

Vulnerabilities

A vulnerability is a weakness or flaw in your website or network. Vulnerabilities can be exploited to damage or compromise customer and other sensitive data, or your site. If your site were a house, a vulnerability would be an open window or door. To protect your house, you'd lock that window or door. Websites and networks have analogous entry points, as well as ways to seal off those entry points for greater protection.

Critical versus informational (non-critical)

While not inherently dangerous, a critical vulnerability leaves your site exposed to serious breaches. For example, someone could gain access to sensitive data, alter your site's appearance or function, or infect your visitors' systems. How critical a particular vulnerability is depends on two things:

1) How commonly exploited the entry point is, and

2) How much damage a breach to that area could cause.

For example, in a house, doors and windows are more commonly exploited than floorboards and chimneys. Similarly, some parts of a website or network are more commonly exploited than others. Some areas also may contain especially confidential or valuable data, so a breach of those parts would be more critical than a breach of other parts.

Vulnerability assessment

When you activate vulnerability assessment, we scan your website or network or both each week for common entry points which, if breached, could threaten your online security. You receive the results of the scan in a downloadable PDF report highlighting the most critical vulnerabilities. Non-critical vulnerabilities are listed in the section labeled "Informational."

You can activate or deactivate vulnerability assessment from within your account. Once you activate vulnerability assessment, your first PDF report should be available for you to download within about 24 hours. After that, we'll run the scan weekly, and generate each new report within about 24 hours of the scan.

Note: Only the presence of critical vulnerabilities (not informational) will trigger an alert in your console. Your report will be available for download each week whether or not you have critical vulnerabilities.

When you are logged into your account, you can set or change your email notification preferences for vulnerability assessment. For example, you can choose to receive notification emails only for critical vulnerabilities, each time a new report is generated, or when we are unable to scan your site. You can also choose email recipients.

Best Practices

To help protect against security breaches, it's recommend that you:

· Activate the vulnerability assessment service.

· If you already have a vulnerability scanning service, use vulnerability assessment as a cross-check for your other scan's results. Scan results can differ from company to company.

· Designate someone in your organization to review each report, and to have any critical vulnerabilities repaired as soon as possible. Set your email preferences to notify your designated person when new reports are available.

· After making repairs, rescan your site to verify the repairs.

· Read and follow the suggestions in the Malware Prevention article below—they also apply to vulnerability.

5 Minutes Guide to Malware

Malware is the new computer virus, the new worm, the new spam. In fact, malware is all of those and more. Malware is a genuine threat to your Web site, to your business, and to your customers. Malware leads to:

Web site traffic loss – New customers are warned about your site and loyal customers stop coming back.
Brand tarnishing – Your company's reputation – not just your Web site – is damaged.
Consumer confidence erosion – Consumers will not trust your Web site, your business, or your products and services.

Instead of overt Internet vandalism and mayhem, today's malware criminals stealthily infiltrate Web sites and home computers for devious or illegal profit.

Their mission: Put malware on your site and spread the malware to your visitors for fraud and theft.

Your mission: Keep malware off your site and keep customers on your site!

Why should I care about malware?

Trust. Your customers and business partners trust that your Web site is safe. Malware on your site diminishes or eliminates that trust.

Customers who are warned of or infected by malware on your site will no longer trust your site or your business. They may stop doing business with you through any means.
If there is malware on your site, Web browsers like Internet Explorer and Firefox and search engines like Yahoo! and Google will show a warning that your site is dangerous when a customer tries to visit it (this is known as "blacklisting").
Malware on your site can install malware on your customers' computers (known as "drive-by downloads"). Malware on your customers' computers can steal their personal information, track their keystrokes and activities, and spread viruses and more malware.

What is malware?

Malware is any computer program that is installed on a computer without the owner's knowledge, in order to deliberately damage the computer or perform illegal activities.

Malware is short for "malicious software". Malware is related to the more well-known term "computer virus", but they are not exactly the same.
Malware is a broad term used to refer to many different forms of hostile, intrusive, or annoying software, such as computer viruses, worms, trojan horses, rootkits, spyware, dishonest adware, and crimeware.

How is malware used?

For illegal profit, consumer deception, Web site vandalism, and other criminal activities.

Adware shows pop-up ads on infected computers and the attackers collect payment based on the number of times the ads appear.
Spam is the bulk junk mail that everyone gets in their Inbox. Spam can be sent from malware-infected computers. The attackers collect payment based on the number of emails sent or on responses to the sales or information requests in the emails.
Identity Theft and Infostealing capture private information, such as usernames and passwords, credit card and banking information, or social security numbers. The attackers can use the stolen data directly to impersonate the theft victim, or sell lists of stolen data within their crime network.

Where does malware come from?

Like a computer virus, malware starts on a few computers and then spreads to many computers.

To effectively distribute malware to as many computers as possible, the first goal of a malware attack is to infect your Web site.
Unknown to you and the people who visit your site, the malware then installs more malware on the visitors' computers.
Installation may be totally invisible to your site visitors – all a visitor needs to do is go to a certain page, and the malware can install on the visitor's computer. Installation may also be disguised as or packaged with a useful plug-in, which the visitor intentionally downloads and installs.

How do I prevent a malware infection?

Keep your web server secure, clean, and backed up.

Maintain an up-to-date backup server.
Secure the Web server that hosts your Web site.
Secure any applications or other code that is executed or distributed on your Web site.
Know and trust the people who manage your Web site.
Remove programs that are not needed.
Do not use the server for other purposes, especially browsing the Web.
Do not rely on commercial, off-the-shelf antivirus services to protect your Web site.
See the Malware Best Practices article for more details on these prevention recommendations.
also read important vulnerability basics

Malware Prevention - Best Practices

Preventing Malware Infections

Preventing malware on your Web site is easier than you might think. And it doesn't require too much extra time, money, and resources to protect your systems. Following best practices for prevention and using the resources that you already have, you can significantly lessen the chances of having malware on your Web site.

Discuss these tips and guidelines with your developers and server administrators. Find out if and how these best practices are applied in your company. Set administrative and development policies based on these best practices as well as the recommendations of your trusted administrators.

Back up your Web server!

Perhaps the most significant preventive measure that you can take is actually preparing for the worst case scenario. What do you do when your Web site is infected and you can't just delete the malware? In that case, you want to make sure that you can recover everything that you use to run your Web site.
Maintain a redundant, up-to-date backup Web server. If your active server is infected, you can switch over to the clean backup server. Your customers will not experience any downtime while you clean the infected server.
If maintaining a redundant backup is cost- and resource-intensive, make sure that you have backup copies of all operating system and application software, including all patches and maintenance releases.
Make especially sure that you regularly back up all of the data. If any business or customer data is compromised or damaged, you can restore the data with minimal downtime for specific features – instead of taking your entire Web site offline.

Secure your Web server.

User access must be secure. Your administrators and developers should use strong passwords, change their passwords regularly, or use access credentials that are handed out by a trusted administrator.
Follow the "principle of least privileges." Know who has access to your server and make sure that only those who need access have it. Additionally, restrict user privileges person-by-person; give your administrators and developers only the privileges that they need to do their job.
File transfers must be encrypted. Use Secure FTP (SFTP) or Secure Copy (SCP) tools to transfer the files. FTP tools are not encrypted.
Practice secure application development. In your back-end code, validate user input type and eliminate security holes (known as "vulnerabilities") such as buffer overflow, SQL injection, and cross-site scripting.
On your customer-facing Web site, don't give away any information that your customers don't need – the information might be useful for attackers. For example, in error messages, don't show your server type or version or say that "we can't connect to the database". Don't provide specific login errors like "your password is wrong" – this message tells an attacker that an account exists with the username.

Trust the person at the keyboard.

Make sure that everyone with access to your Web server understands and recognizes social engineering methods. Social engineering is convincing someone to do something or reveal confidential information, typically by impersonating a person of authority or influence. A saying goes: "it's easier to hack the person than it is to hack the machine".
Through social engineering, a malware attack starts without even touching your Web server. With just a little information about your company, an attacker can impersonate a company executive or external authority (such as the police or a lawyer) over the phone. If the attacker is convincing enough, the attacker might persuade a junior developer to unknowingly install or link to malware.
Have confidence in and trust all of the people who have access to your Web server. But regardless of your level of trust, your server should track user logins and all actions while logged in.
Trust and accountability are key to preventing the most direct threat – an inside job, a deliberate attack by an employee or colleague. Whether driven by personal reasons or coerced by an outsider, this person already has all of the access and privileges needed to put malware on your Web site.
For any changes to your Web site, have a clear sign-off process. You should also have contingency plans if critical people are not available, so that everyone knows what to do when you or your server administrator can't be reached.

Use your Web server for one thing and one thing only: running your Web site.

Do not use the server to browse the Web, check your email, instant message, blog about your vacation, or send your mom photos from last week's family reunion. You have enough to worry about with attackers trying to get in – don't help them out by actively roaming the Internet.
Remove all unused programs from your Web server. Popular applications sometimes have known vulnerabilities that attackers can easily exploit. If a program is not being used, remove the program so that it is not a potential point of attack.
If possible, remove software documentation from the server and store it elsewhere. Documentation that includes application names, version numbers, and bug fixes can give attackers insight into what's on the server and how to gain access.

Patch, patch, patch. Keep your server software, operating systems, and applications up to date.

Know what software is on your server. Keep a list of all operating system and application software installed on the server, including version numbers.
Keep all software on the server up to date and running the current versions. Newer versions often include fixes for known vulnerabilities. Vulnerability fixes close the loopholes that the hacker and malware communities know how to exploit.

See Malware Basics and 5 mins guide to Malware