What is Threat Modeling

“If you know the enemy and know yourself, you need not fear the result of a hundred battles. If you know yourself but not the enemy, for every victory gained you will also suffer a defeat. If you know neither the enemy nor yourself, you will succumb in every battle.”

….. Sun Tzu

Threat is an undesirable situation where a possibility exists that a threat agent or actor can intentionally or unintentionally exploit a vulnerability that exists in a system. The vulnerability can be technical or non-technical. Threat modelling is technique to visualise all such undesirable situations in a single frame in the ecosystem in which the system is supposed to function. In simple terms it is finding “what all can go wrong and why and how”.

Threat modeling is primarily used during systems development to anticipate and neutralize the threats. These threats are mostly technical and solutions expected would be technical. This type of modeling is also called application threat modeling. Microsoft’s STRIDE (Spoofing identity, Tampering with data, Repudiation, Information disclosure, Denial of service and Elevation of privilege) categorization used in SDLC is a popular model which starts off with the requirement of Data Flow Diagram(DFD) of the Application.  This is used by “Microsoft Threat Modeling Tool 2014”. This model can also be used for existing application to address threats in its working environment. Threat modeling will result in a comprehensive document of threat enumeration and analysis with mitigation solutions.

In relation to SDLC (software or system development life cycle), it does not avoid code review but helps in focusing on critical issues so that time and efforts are minimised. Therefore it is a Risk based approach. The process helps in systematically documenting the attack surface. Threat modeling is not a panacea for system compromise attempts and in no way it should be considered as an encouragement to develop complex systems with spaghetti code. In my opinion “KISS” (Keep It Simple Stupid) is the ultimate advice to avoid security problems. Simplicity dramatically reduces the attack surface.

Threat modelling is closely related to attack trees. Attack trees were actually popularised by Bruce Schneier in 1999. However the purposes for which they have evolved are quite different. These two have the following different approaches:

Threat Modelling

• Application or system oriented. May be asset oriented. Extrapolated from characteristics of systems, their interfaces, connections and flow of data between them.  Threat modeling is the general term used in such cases and uses DFDs. This process is also termed as Tool assisted code review.
• Primarily used for risk management during application or system development by enumerating attack surfaces.

Attack Trees

• Attacks and attacker oriented. Extrapolated from predicted behavior of attackers and the multiple paths they can follow.  Attacker will focus on Intended and unintended behavior of the system. Attack trees, Threat trees or Misuse case or Abuse trees are generally used. In an Attack tree the whole attack process is synthesized and shown as set of possible steps. Attack trees have tree structure with child nodes using AND and OR operators and the parent node being a attackers ultimate goal.
• Primarily used for risk management of a already deployed and in use application or a system. This can be done on periodical basis whenever there is a significant change in technology or threat landscape.

We all do threat modeling every day for risks associated with our daily activities.  We do it in our own creative way.  Then why do we need these models? These are organized, structured and documented activities.  How useful are these organized activities? Well the chances of some known attacks or compromises would reduce but would not make the system completely attack proof Threat Modeling should be holistic for best results. Brain storming and group discussions should be used over and above the analysis provided by a tool. 

Threat Categorization Frameworks

• STRIDE - Spoofing identity, Tampering with data, Repudiation, Information disclosure, Denial of service and Elevation of privilege (high level categorisation)
• DREAD - Damage, Reproducibility, Exploitability, Affected users and Discoverability (Attacker's point of view)
•  ASF - Application Security Frame
• CAPEC - Common Attack Pattern Enumeration Classification

Pros and Cons of Threat Modeling.

           Pros

A systematic and recorded process

Will give a headway

Great for people who just initiated into the security world

A fast method to address known exploitation methods( Attack vectors)

           Cons

False sense and confidence of having dealt with all possible threats, attack         vectors and vulnerabilities

May limit thinking boundaries and limit free flow of ideas to visualise all possible   bad scenarios 

A simple two tier web application threat modelling using Microsoft’s Threat modelling Tool which is based on STRIDE.

Tools

• Trike framework and tool for risk management 
• Microsoft Threat Modeling Tool 2014  
• Seasponge
• Seamonster  
• SecurITree by Amenaza  
• ThreatModeler by MyAppSecurity

References

·         https://msdn.microsoft.com/en-us/library/ff649461.aspx

·         https://www.amenaza.com/downloads/docs/AttackTreeThreatRiskAnalysis.pdf

    https://www.owasp.org/index.php/Application_Threat_Modeling

SCADA AUDIT

AUDITING SCADA SYSTEMS
Introduction

SCADA (supervisory control and data acquisition) is a system operating with coded signals over communication channels so as to provide control of remote equipment (using typically one communication channel per remote station)                       en.wikipedia.org/wiki/SCADA
Industrial control systems (ICS) are computer-based systems that monitor and control industrial processes that exist in the physical world. SCADA systems historically distinguish themselves from ICS systems by being large-scale processes that can include multiple sites, and large distances. SCADA can be considered class of ICS.
Originally, SCADA systems were not connected to the Internet. Security was traditionally not an issue in SCADA systems. However the same is not true now.
Where is SCADA used?
Electric power generation, transmission and distribution
Water and Sewage network systems
Environment and facility monitoring and management
Transportation networks
Manufacturing processes

Functions of SCADA
DATA ACQUSITION- Furnishes status information & measures to operator
CONTROL - Allows the operator to control the devices e.g. circuit breakers, transformers, tap changer etc from a remote centralised location.
DATA PROCESSING - Includes data quality & integrity check, limit check, analog value processing etc.
TAGGING - Operator can identifies any specific device & subjects to specific operating restrictions to prevent from unauthorized operation
ALARMS - Alerts the operator of unplanned events & undesirable operating conditions in the order their severity & criticality
LOGGING- Logs all operator entries, alarms &selected entries
TRENDING- Plots measurements on selected scale to give information on the trends e.g. one minute, one hour etc.
HISTORICAL REPORTING - To save & analyze the historical data for reporting, typically for a period of 2 or more years & to archive.

SCADA Components and Subsystems
SCADA has following components:
1.             Operating equipment: pumps, valves, conveyors, and substation breakers that can be controlled by energizing actuators or relays.
2.                  Local processors: communicate with the site’s instruments and operating equipment. This includes the Programmable Logic Controller (PLC), Remote Terminal Unit (RTU), Intelligent Electronic Device (IED), and Process Automation Controller (PAC). A single local processor may be responsible for dozens of inputs from instruments and outputs to operating equipment.
3.                  Instruments: in the field or in a facility that sense conditions such as pH, temperature, pressure, power level, and flow rate.
4.                  Short-range communications: between local processors, instruments, and operating equipment. These relatively short cables or wireless connections carry analog and discrete signals using electrical characteristics such as voltage and current, or using other established industrial communications protocols.
5.                  Long-range communications: between local processors and host computers. This communication typically covers miles using methods such as leased phone lines, satellite, microwave, frame relay, and cellular packet data.
6.                  Host computers Human–Machine Interface or HMI: act as the central point of monitoring and control. The host computer is where a human operator can supervise the process, as well as receive alarms, review data, and exercise control.
                                                       
 Sub Systems
• Supervisory system
• HMI
• RTU
• PLC
• Communication Interface
• SCADA programming


SCADA vendors
Some SCADA vendors are Asea Brown Boveri(ABB), Siemens, Alstom ESCA, Telegyr Systems, Advanced Control Systems(ACS), Harris and Bailey.




SCADA protocols
SCADA protocols are communications standards to pass control information on industrial networks. There are many of these protocols but prominent ones are MODBUS, DNP3, EtherNET/IP, PROFIBUS, IEC 61850 and Foundation Fieldbus. The choice of protocol is based on operating requirements, industry preference, vendor and the design of the system. In an oil refinery an operator workstation might use the MODBUS/TCP protocol to communicate with a control device such as a Programmable Logic Controller (PLC). Alternatively, in power utility’s SCADA system, a master located in a central facility could use the DNP3 protocol to query and control slave Remote Terminal Units (RTU) distributed in remote sub-stations. Some other protocols are: ICCP, ZigBee, C37.118, and C12.22
Known Issues
1.         In a SCADA system, the programmable logic controllers (PLCs) are directly connected to infield sensors that provide data to control critical components (e.g. Centrifugal or turbines). Often the default passwords are hard-coded into Ethernet cards the systems use. Those cards funnel commands into devices, allowing administrators to remotely log into the machinery. Hard-coded passwords are a common weakness built into many industrial control systems, including some S7 series of PLCs from Siemens. Hardcoded or saved passwords are also found in windows registry of various host machines. PLCs and RTUs are web enabled for remote access and this creates a window of opportunity for attackers.

2.         Lack of Authentication and medium control in SCADA systems is another major issue. Investigation of past SCADA incidents demonstrated that mobile storage mediums are the main vectors used to infect control systems, despite that host networks being isolated from the Internet. Establishing strong controls on every medium used could prevent serious incidents. Strong authentication must be implemented to ensure secure communication, and to allow personnel to access main functionalities provided by systems. The administration console for any network appliance must be protected. Wireless and wired connections to the SCADA network and remote sites must be properly defended.



Steps to perform an audit
1.      Identify all connections to SCADA networks. Evaluate security of connections. Identify systems that serve critical functions.
2.      Conduct VA  of Network Connectivity by mapping of all networked assets and the digital communication links that connect them
3.      Check for default settings and configurations of all systems
4.      Check for unnecessary services
5.      Check if  security features provided by device and system vendors  are effectively activated.
6.      Check  authentication and medium control.
7.      Check for proper network segregations.
8.      Check internal and external intrusion detection systems
9.      Check if  24-hour-a-day incident monitoring takes place
10. Perform technical audits of SCADA devices and networks, and any other connected networks, to identify security concerns
11. Conduct physical security surveys and assess all remote sites connected to the SCADA network to evaluate their security
12. Identify and evaluate possible attack scenarios
13. Check if  cyber security roles, responsibilities, and authorities for managers, system administrators, and users  have been defined.
14. Check for ongoing risk management process
15. Check for configuration management processes
16. Scrutinise routine self-assessments  reports
17. Check for system backups and disaster recovery plans and BCP
18. Check for  availability of  policies
19. Interview all key personnel
Tools

SamuraiSTFU, plcscan, modscan, metasploit, Nessus, nmap, wireshark, tcpdump, modlib(scapy extension), Bus-pirate, CERT NetSA Security Suite, NetWitness, Lancope, Arbor, 21CT, Checkmarx, Contrast Security, Burp Suite Professional, NTOSpider, Netsparker, Appscan, sqlmap, Zulu, GPF/EFS, PFF, ImmDbg, Sulley, gdb, MSF, RTL-SDR/HackRF plus GNURadio/RFCat, binwalk, IDA Pro etc etc

https://www.thalesgroup.com/sites/default/files/asset/document/thales-cyber-security-for-scada-systems.pdf

http://resources.infosecinstitute.com/improving-scada-system-security/

Data Loss / Leak Prevention

Strictly speaking data  “Loss” can be due to machine failure, power failure, data corruption, data / media  theft etc and the means of protection is backups, disaster recovery strategies and redundancies.

Though “L”  is used to represent either  “Loss” or “Leak” in the acronym DLP, it is actually more about “LEAK”  as it is understood in the industry. Which actually  means sensitive data crossing over to unauthorized area from a authorized area due to various leak vectors.

DLP is actually more of a concept or strategy with functional sub components (e.g  email scanning, encryption of data at rest and so on). These components are used to enforce the strategy outlined by policy statements. Such policies can be

• Acceptable use policy( AUP),  
• Data sharing on detachable/portable media  policy, 
• Data classification policy,  etc

DLP is actually part of IRM (Information Risk Management). Data sanitation, using test data and  Data masking is also part of DLP strategy.

However, we have DLP tools which claim to handle all functionalities of DLP strategy and therefore some technologists believe that by just deploying such tools  DLP is implemented.  This is grossly wrong.  DLP is more about strategy, awareness,  training  plus the technology. Data leak more often than not happens due to poor employee discipline or awarness.

DLP addresses three areas

• ·         Data at rest ,    e.g data in databases, data on a drive of a laptop / usb storage
• ·         Data in transit,   e.g  emails or web forum postings, upload to cloud, data on network
• ·         Data in use, e.g  file copy or print operations

Output actions of a DLP tool:

• Quarantine, 
• encrypt, 
• block, 
• notify

DLP Tool is deployed at end points,  email gateways, network gateways for url filtering.

Sub functions or processes of DLP  tool are:

• Monitor, 
• Detect and 
• Prevent

DLP tools are good at monitoring structured data as in  PII(Personally Identifiable Information) and as in PCI(Payment card industry)  but they are difficult to use for unstructured data.

For data at rest Data discovery or discovery scanning is used. Pattern matching or string comparison is used for structured data. hashing is generally used for unstructured data.

Before a DLP tool is deployed one should clearly define  and identify the sensitive data which need protection and also all possible  internal and external threats

A Checklist

1. Policies and user awareness campaigns.
2. Encryption for data at rest and in transit.
3. File shares mapped  with access rights.
4. Consolidation of inventories.
5. Control of  external HDD and usb storages devices (mobile and portable storage devices)
6. Disabling of all usb ports for usb storage devices.  
7. Disabling of all unwanted  inbuilt DVD readers/writers.
8. Air gap maintenance  disconnected networks.
9. Secure  file delete policies and procedures.
10. Access controls on laptops and full disk encryption.
11. Use of  VLANS
12. Consolidation of file servers 
13. Strict data classification policies.
14. Data retention policies. Destruction of old and unwanted data files.
15. Deploying RMS/DRM/IRM  solution
16. PKI based email  
17. Effective Identity provisioning and management.
18. Content and Gateway screening

Presentations

Social Engineering

Layer Two Security

Email Best Practices

How Trustworthy are Mobile Apps or Applications ?

   Have a look at the the permissions being asked by these Andriod Apps. What do you make out of these snapshots? Which App is more secure - not from the point of view of security for the App but security for the user who downloads and uses them. The one on the extreme left(first one) is likely to have more access to your device than the other two. The makers would argue that these permissions are required for the features and functionality of the App. The question here is who will decide how much permission is required and who will guarantee that these permissions would not be abused. The one on the extreme right-bottom is more trustworthy as it requires no special permissions. But how many of us really pay any attention to such details?

    Unlike the applications on a Desktop, with mobile apps it is difficult to find what they are really doing behind the scenes. The situation is compounded by the fact that the mobile devices contain enormous amount of personal, sensitive and financial data. The email apps are always online.The device is always connected to internet in most cases. The passwords and others credentials are just there begging to be stolen away.

   Personally i prefer to use my browser on my mobile to access the various web sites and web applications rather than download an App. Re-entering usernames and passwords every time you access an web application or a website should not bother you if your are worried about safety of your data and online identity.

    Having written what i wanted to convey, i would like to clarify that i am not aware that the above mentioned Apps are untrustworthy in anyway. I just picked them up for an illustration.

ISO 27001 : 2013 Changes

                                            

	ISO 27001:2005	ISO 27001:2013
1	Annex A :has 133 controls	Annex A : has 114 controls 11 new controls A.6.1.5 Information security in project management A.12.6.2 Restrictions on software installation A.14.2.1 Secure development policy A.14.2.5 Secure system engineering principles A.14.2.6 Secure development environment A.14.2.8 System security testing A.15.1.1 Information security policy for supplier relationships A.15.1.3 Information and communication technology supply chain A.16.1.4 Assessment of and decision on information security events A.16.1.5 Response to information security incidents A.17.2.1 Availability of information processing facilities
2	Annex A: 11 control objectives	Annex A: 14 control objectives (A5 to A18)
3	Five implementation sections ·         4-ISMS ·         5-Management  responsibility ·         6-Internal  ISMS  audits ·         7-Management review  of  the  ISMS ·         8-ISMS  improvement	Seven implementation sections ·         4-Context ·         5-Leadership ·         6-Planning ·         7-Support ·         8-Operation ·         9-Evaluation ·         10-Improvement
4	Non standard format	Annex SL format(MS standard)
5	Process based approach	Non process based
6	Structured around PDCA deming cycle	No emphasis on PDCA cycle
8	Separate class of ‘Preventive’ controls	‘Preventive’ controls removed
9	Requires ‘Documents’ and ‘Records’	Instead requires ‘Documented Information’
10		Parts derived from ISO 31000:2009 Risk mgmt
11	‘control objectives and controls from Annex A shall be selected and implemented’	‘produce a “statement of applicability(SOA)” that contains the necessary controls’
12	Has Annex A, B and C	Has Annex A
13		New important term ‘Risk owner’
14	Emphasis on documentation of Internal Audits	No need to document internal audit

Information security quotes for awareness

• "Security has a group ownership                  --not individual ownership"....G.R
• "Tech Savvy does not mean                  --security conscious"

• "Technology cannot replace security good habits"

• "Simple and elegant the solutions                   -- better is the security"

• "Money can buy security products                   -- but not security" ....G.R

• "Security is not a product                                -- it is a process" ... Bruce Schneier

• "We will forgive the breach                            -- but not the silence" 

• "If you want PRIVACY             -- then maintain private posture and not public posture" 

• "High security means                -- right awareness"....G.R

• "Best medicine for security diseases is  -- high dosage of awareness"....G.R
•  "Technology is just a security enabler           -- not a security ensurer"  ....G.R 
• "Trust can be absolute                        -- but Security cannot be absolute".......GR.
• "Stop - Read and Click".........GR
• "Technology alone may not protect you better
                                       --but  awareness about the correct usage of technology may protect you better"....G.R

Maintain Online Privacy. How to do that?

   One of the big issues of online activities is to maintain a right balance of information that is voluntarily shared with information that is not shared. However, there is a general agreement or baseline which tells us what is private information. This baseline would contain recommendations like donot share private telephone number; do not share primary email id etc etc.

    This perceived privacy posture may vary from person to person. The privacy settings and features on many sites and applications are provided in a elaborated fashion these days. But these keep changing very often and it is very difficult for a user to keep track and manage them. Therefore what one needs do is follow three simple rules:

    Rule 1: Initially assume everything is private information


    Rule 2: Always share or post only when required and only with few(required)
                  people

    Rule 3: Remove, rename, modify all information that can be traced to you,
                   identify   you  or identify your activities.


This link can be used to directly access the privacy setting features of your favourite  application.            http://adjustyourprivacy.com/

Next 5 biggest Info sec challenges

In my previous post I had listed the biggest 5 challenges. The challenges listed in this post are the next  five.

6.  Formulating and Enforcing data classification data destruction policies

Data discipline in terms of classification and management which would include labelling for archiving or disposal/ destruction is still quite casual by end users who generate documents. Though most users understand such policies for hard copies or physical documents and implement them to a large extent, they fail to do so for digital data. Duplicate and uncontrolled versions  of unstructured data(e.g word documents) lead to quite a few embarrassing situations.


7.   Consolidation and leverage of user initiated software systems

In a reasonably big, diverse and geographically wide spread enterprise the local IT people tend to design and use their own software tools. In such cases the overall organisation requirements  are not the issue but day to day task achievements are the goals. Consolidation and control of these from an ISMS point of view is often overlooked by central IT management. The local IT people also resist such attempts most of the time.

 8.   Disposal of old and decommissioned IT assets

Not much thought is given to old and decommissioned systems and they become a sore point. This happens despite having policies and regulations on the subject. 

9.   Individualistic continuance of IT initiatives and their management

Continuous dependence on such individuals would definitely lead to security issues in future. Processes should be evolved for managing these systems and after giving due credit such  individuals  should be taken away from these projects.  

10.  IT asset ownership issues

This topic continues as a thorn and requires resolution by regular education and awareness  programs.

5 Biggest Challenges in Information Security Management

Based on my past experiences in implementing ISMS as an Information security Manager, I would rate the following as the biggest five challenges

1.  Attitude or the prevailing culture:
The responsibility of implementing and ensuring security automatically qualifies one as  "not so friendly" for computerisation and IT services. The top management(c-level) want you to implement and drive the policies and strategies but general employees who are end users of the various IT assets want minimum barriers and maximum convenience.

You end up sandwiched between both the parties hating you as you are not listening to them. It takes time and considerable effort to change attitude and culture for better cyber security health  although it is worth the effort. Surmounting such attitudes and changing the culture is the biggest challenge.

2. Technology as a solution:
Every medical problem does not have a medicine. Even if there are medicines available, they may not treat you completely. You do not rule out the side effects of the medicines though advances are being made everyday.

Similarly technology alone is not a complete security solution. Just the other day we heard of google getting affected due to  redundant network path failures simultaneously.
The ultimate success and efficacy of any security program will always be due to people, procedures and processes in conjunction with technology.

Most management and end users still perceive technology and products as the magic bullet. Breaking this myth is the next  biggest challenge.

3. Incorrect priorities:
CIA which stands for Confidentiality, Integrity and Availability is not clearly understood. Every functional organisation and every department needs to understand which one element is more important than the other two or one. Giving equal priority to all the three aspects may hamper the work  output and operations and would lead to unnecessary friction. Security professionals need to understand this and should advise accordingly.

4. Under Staffing:
The next biggest challenge is of under staffing. Though the situation in IT per say has improved to some extent, the situation in security remains grim. Senior management needs to appreciate this and provide sufficient staff to overlook information security.

5. Skill Retention:
The last of the five challenges in my opinion is of skill retention or continuity of job for lower level of Information security staff who are actually responsible to translate the policies and decisions into actions.  Insufficient skill and under staffing  not only increase the implementation gaps but also increase the stress level of the IT security staff.

Dangers of Geotagging and Location Aware Services

Every new and wonderful technology feature brings along its share of undesired effects bundled with the effervescent benefits. Geotagging or Geo Tagging is one such feature. To explain Geotagging in simple terms, it is nothing but including geographical information(location data) as tag within a file. These files can be of any type but mostly picture files are geotagged.

Why has geotagging suddenly become so prominent?
Smartphones and cameras with  GPS (Global Positioning System) feature is the norm now-a-days. By default the GPS location data is embedded into all the pictures taken by these devices. In addition you have location aware applications and games and location based social networking sites/platforms. Facebook uses "Update Status" for location update. Foursquare is a game wherein in your location is the integral part of the gaming strategy. There are software available which can add location data to picture and other files if this was not done inherently.

What can be bad about Geotagging and location data?
If you indiscriminately share geotagged pictures, SMSs and other files and update your current location in applications like Facebook then you are revealing too much of your whereabouts to the public at large. You can become a victim of cyberstalking. Burglars can target your house when you tweet that your are away somewhere in the woods enjoying a sunday picnic. In fact your are giving away information about your pattern of movements, place of residence and other such details for free and putting yourself and your family at risk. Kids who share photos and tweet on twitter a lot without giving a thought about the broadcasted location information may land up as victims of serious crimes.

It is important that all of us are aware of the dangers of this feature and know how to adopt the countermeasures. The most important countermeasure is to avoid oversharing. The default configurations which automatically include location data or tags need to be disabled or changed. The specific tips are listed on the SECURITY TIPS page.

Interesting links on the topic :
 http://icanstalku.com  
 http://www.geotagsecurity.com  

Information Security Quotes

Usually it is very difficult to spread security awareness amongst normal users or general public using technical jargon.  As many others already know, I have also realised that simple Sayings or Quotes in simple language aptly convey the required message and come to your rescue. I have created a separate page to list such Information Security quotes. I will update and increase the list subsequently.

Wireless or WiFi Security

Wireless or WiFi security from a normal users point of view is as important as anything else. With WiFi enabled mobiles, gaming devices the environment becomes much more dangerous. I have listed some useful tips on my "Tips and Tricks" page.

What is a "Good and strong" password and other questions.

1. What is a good password?

There is a vast difference between a "good and strong" password and a "complex" password. 'Ab%98@#k*t5z' is a very complex and strong password but is a bad password because it is very hard to remember. However, 'Blacck>Mang0s' is a strong as well as a good password because you can easily remember it. It is strong because it is of sufficient length and is a combination of lower case, upper case, special character and numerals. Passphrase or related characters like above would be good.The other requirement is that of sufficient length, 10 or more characters.

2. Can  a Antivirus product detect all malware in existence?

This is simply not possible techinally, whatsoever the vendors may claim. However, some poducts may be better at any given time. The detection rate of even the best product may be not more than 85%.


3. Which is best anti-virus?

For commercial software go by the existing market reputation. But, be careful, a recently reported news mentions about an emerging antivirus product which induced malware and subsequently cleaned them to generate a good scan report. If you are using freeware then check for the reputation or popularity. Download these from a trusted source.


4. Is  an Antivirus still required if a firewall is used and vice versa?

Both have a different but comlimentary fuction. You require both to safeguard your computer. If a malware is able to breach your firewall then at least the Antivirus would have a chance to detect it.


5. What if the AV has not detected the malware and someone is remotely controlling or using my computer?

If your are a normal user then nothing much can be done except to attempt manually cleaning the offending software. The best option would be to go back to a previous checkpoint, or reinstall the OS after you have taken a backup. Before such a step, take a chance with the free tools i have listed on the right side of this post. Experienced users can use the tools mentioned in my prevoius post.


6. Enabling all the Browser security features has blocked my critical banking and email site?

There is no absolute '0' or '1' answer to this question. Depending on a users requirements and his web browsing habits he may have to customise the settings slowly over a period of few days. Disabling java may have led to your bank account page being rendered useless. You need to figure out this and enable java specifically for this site.