10 research outputs found

    How Do You Secure an Environment Without a Perimeter? Using Emerging Technology Processes to Support Information Security Efforts in an Agile Data Center

    Get PDF
    Cloud computing has transformed businesses, enabling agile and cost-effective IT infrastructure. The critical problem is that these new opportunities resulted in a co-mingled architecture which is difficult to secure. Based on interviews with boards of directors and executive leadership teams facing these new environments, our research question was: How do we secure increasingly dynamic architecture in an environment without a perimeter? The research involved an in-depth exploration of this problem using a survey instrument and interviews with 204 executives from 80 companies throughout 2014. From this work we developed an information security framework for executives in this new environment

    Intrusion detection and prevention of web service attacks for software as a service:Fuzzy association rules vs fuzzy associative patterns

    Get PDF
    Cloud computing inherits all the systems, networks as well asWeb Services’ security vulnerabilities, in particular for software as a service (SaaS), where business applications or services are provided over the Cloud as Web Service (WS). Hence, WS-based applications must be protected against loss of integrity, confidentiality and availability when they are deployed over to the Cloud environment. Many existing IDP systems address only attacks mostly occurring at PaaS and IaaS. In this paper, we present our fuzzy association rule-based (FAR) and fuzzy associative pattern-based (FAP) intrusion detection and prevention (IDP) systems in defending against WS attacks at the SaaS level. Our experimental results have validated the capabilities of these two IDP systems in terms of detection of known attacks and prediction of newvariant attacks with accuracy close to 100%. For each transaction transacted over the Cloud platform, detection, prevention or prediction is carried out in less than five seconds. For load and volume testing on the SaaS where the system is under stress (at a work load of 5000 concurrent users submitting normal, suspicious and malicious transactions over a time interval of 300 seconds), the FAR IDP system provides close to 95% service availability to normal transactions. Future work involves determining more quality attributes besides service availability, such as latency, throughput and accountability for a more trustworthy SaaS

    Hosting critical infrastructure services in the cloud environment considerations

    Get PDF
    Critical infrastructure technology vendors will inevitability take advantage of the benefits offered by the cloud computing paradigm. While this may offer improved performance and scalability, the associated security threats impede this progression. Hosting critical infrastructure services in the cloud environment may seem inane to some, but currently remote access to the control system over the internet is commonplace. This shares the same characteristics as cloud computing, i.e., on-demand access and resource pooling. There is a wealth of data used within critical infrastructure. There needs to be an assurance that the confidentiality, integrity and availability of this data remains. Authenticity and non-repudiation are also important security requirements for critical infrastructure systems. This paper provides an overview of critical infrastructure and the cloud computing relationship, whilst detailing security concerns and existing protection methods. Discussion on the direction of the area is presented, as is a survey of current protection methods and their weaknesses. Finally, we present our observation and our current research into hosting critical infrastructure services in the cloud environment, and the considerations for detecting cloud attacks. © 2015 Inderscience Enterprises Ltd

    Detecting and mitigating HX-DoS attacks against cloud web services

    Full text link
    Cyber-Physical Systems allow for the interaction of the cyber world and physical worlds using as a central service called Cloud Web Services. Cloud Web Services can sit well within three models of Cyber- Physical Systems, Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a- Service (IaaS). With any Cyber-Physical system use Cloud Web Services it inherits a security problem, the HX-DoS attack. HX-DoS attack is a combination of HTTP and XML messages that are intentionally sent to flood and destroy the communication channel of the cloud service provider. The relevance of this research is that TCP/IP flood attacks are a common problem and a lot of research to mitigate them has previously been discussed. But HTTP denial of service and XML denial of service problem has only been addressed in a few papers. In this paper, we get closer to closing this gap on this problem with our new defence system called Pre- Decision, Advance Decision, Learning System (ENDER). In our previous experiments using our Cloud Protector, we were successful at detecting and mitigate 91% with a 9% false positive of HX-DoS attack traffic. In this paper, ENDER was able to improve upon this result by being trained and tested on the same data, but with a greater result of 99% detection and 1% false positive

    Déni-de-service: Implémentation d'attaques XML-DOS et évaluation des défenses dans l'infonuagique

    Get PDF
    RÉSUMÉ L’infonuagique est un paradigme informatique dont la popularitĂ© et les usages n’ont fait que croĂźtre ces derniĂšres annĂ©es. Il doit son succĂšs Ă  sa grande adaptabilitĂ© et capacitĂ© de mise Ă  l’échelle, ainsi qu’à sa facilitĂ© d’utilisation. Son but est de permettre Ă  l’individu ou Ă  l’entreprise d’utiliser des ressources informatiques qu’il ou elle ne possĂšde pas physiquement, en utilisant des techniques dĂ©jĂ  connues et Ă©prouvĂ©es comme la virtualisation et les services web. Plusieurs modĂšles d’infonuagique existent, selon la fonctionnalitĂ© recherchĂ©e. Par exemple, dĂ©poser, partager et accĂ©der depuis n’importe quel terminal un fichier sur Dropbox, et exĂ©cuter une application extrĂȘmement gourmande en ressources sur une machine louĂ©e le temps de l’exĂ©cution sont deux exemples d’utilisation de l’infonuagique. Le modĂšle d’infonuagique influe sur la portion des ressources gĂ©rĂ©es par l’utilisateur, en comparaison des ressources gĂ©rĂ©es par le fournisseur. Dans le cas de Dropbox, l’utilisateur n’a pas besoin de se soucier des ressources allouĂ©es Ă  sa requĂȘte ni de savoir quel systĂšme d’exploitation a servi ou encore comment est gĂ©rĂ©e la base de donnĂ©es, alors que dans l’autre cas tous ces paramĂštres rentreront probablement en compte et seront donc Ă  la charge de l’utilisateur. Un rĂ©seau d’infonuagique peut tout autant ĂȘtre un rĂ©seau public accessible de tous moyennant finances, qu’un rĂ©seau privĂ© bĂąti et utilisĂ© seulement par une entreprise pour ses propres besoins. L’attrait considĂ©rable de l’infonuagique, pour les particuliers comme pour les entreprises, augmente par le fait mĂȘme les risques liĂ©s Ă  la sĂ©curitĂ© de ces rĂ©seaux, ceux-ci devenant une cible de choix pour les attaquants. Ce risque accru alliĂ© Ă  la confiance que l’utilisateur doit porter au fournisseur pour gĂ©rer et protĂ©ger ses donnĂ©es explique que nombreux sont ceux encore rĂ©ticents Ă  utiliser l’infonuagique, que ce soit pour des questions de confidentialitĂ© pour une entreprise ou de vie privĂ©e pour un particulier. La diversitĂ© des technologies utilisĂ©es implique une grande variĂ©tĂ© d’attaques possibles. Notamment, les rĂ©seaux d’infonuagique pĂątissent des mĂȘmes vulnĂ©rabilitĂ©s que les rĂ©seaux conventionnels, mais Ă©galement des failles de sĂ©curitĂ© liĂ©es Ă  l’utilisation de machines virtuelles. Cependant, ces menaces sont dans l’ensemble bien connues et la plupart du temps des mesures sont mises en place pour les contrer. Ce n’est pas le cas des vulnĂ©rabilitĂ©s liĂ©es Ă  l’utilisation des services web, utilisĂ©s abondamment dans le cas de l’infonuagique. Les rĂ©seaux d’infonuagique se donnent pour but d’ĂȘtre accessibles depuis n’importe oĂč et n’importe quel appareil, ce qui passe nĂ©cessairement par l’utilisation de services web. Or les serveurs web sont extrĂȘmement vulnĂ©rables aux attaques de type XML-DoS, mettant Ă  profit des requĂȘtes SOAP (Simple Object Access Protocol) utilisant un message XML malveillant. Ces attaques ont pour but d’utiliser une trĂšs grande partie si ce n’est pas toutes les ressources CPU et mĂ©moire de la machine hĂ©bergeant le serveur web victime, la rendant indisponible pour des utilisateurs lĂ©gitimes, ce qui est le but recherchĂ© lors d’une attaque de dĂ©ni de service. Ces attaques sont extrĂȘmement intĂ©ressantes d’un double point de vue. Elles sont tout d’abord trĂšs difficiles Ă  dĂ©tecter, car l’utilisateur qui en est Ă  l’origine est perçu comme un utilisateur lĂ©gitime (attaque au niveau de la couche application, donc impossible de la dĂ©tecter au niveau de la couche TCP/IP). De plus, elles prĂ©sentent une dissymĂ©trie importante entre les ressources dont l’attaquant a besoin pour monter l’attaque, et les ressources nĂ©cessaires pour traiter la requĂȘte. En effet, une requĂȘte SOAP mal formĂ©e bien que trĂšs basique peut dĂ©jĂ  demander des ressources considĂ©rables au serveur web victime. Ce type d’attaques ayant Ă©tĂ© assez peu Ă©tudiĂ©, malgrĂ© son efficacitĂ© et l’omniprĂ©sence des services web dans l’infonuagique, nous nous sommes proposĂ© de dĂ©montrer et de quantifier l’impact que peuvent avoir ces attaques dans le cadre de l’infonuagique, pour ensuite proposer des solutions possibles pour s’en dĂ©fendre. Nous avons jugĂ© qu’il Ă©tait plus appropriĂ© de recourir Ă  des outils de simulation pour mener nos travaux, pour plusieurs raisons comme notamment la possibilitĂ© de suivre de façon prĂ©cise l’évolution des ressources des diffĂ©rents serveurs du rĂ©seau, et la plus grande libertĂ© qui nous Ă©tait laissĂ©e de construire notre propre topologie. Notre premiĂšre contribution est de mettre en avant les Ă©quipements vulnĂ©rables dans un rĂ©seau d’infonuagique, et les diffĂ©rentes façons de les attaquer, ainsi que les diffĂ©rents types d’attaques XML-DoS. Cette analyse nous a permis d’apporter notre deuxiĂšme contribution, qui consiste Ă  utiliser et Ă  modifier en profondeur un simulateur d’infonuagique (le simulateur GreenCloud, basĂ© sur le simulateur NS2) afin de le rendre apte Ă  l’étude des attaques XML-DoS et plus rĂ©aliste. Une fois ces changements effectuĂ©s, nous montrons l’efficacitĂ© des attaques XML-DoS et les rĂ©percussions sur les usagers lĂ©gitimes. Par ailleurs, nous rĂ©alisons une comparaison critique des principales dĂ©fenses contre les attaques XML-DoS et contre les services web en gĂ©nĂ©ral, et sĂ©lectionnons celle qui nous semble la plus pertinente, afin de la mettre Ă  l’épreuve de la simulation et de mesurer son efficacitĂ©. Cette efficacitĂ© doit ĂȘtre dĂ©montrĂ©e aussi bien en terme de capacitĂ© Ă  dĂ©jouer l’attaque menĂ©e Ă  l’étape prĂ©cĂ©dente, que de prĂ©cision en terme de "false positives" et "false negatives". Un des dĂ©fis majeurs consiste en effet Ă  concilier une dĂ©fense qui se veut universelle pour toutes les machines du rĂ©seau, tout en Ă©tant capable de s’adapter Ă  la grande hĂ©tĂ©rogĂ©nĂ©itĂ© des services web qui cohabitent au sein d’un rĂ©seau d’infonuagique. Ces expĂ©rimentations sont alors l’objet de discussions et de conclusions sur la position Ă  adopter quant aux attaques XML-DoS dans les rĂ©seaux d’infonuagique, notamment les dĂ©fenses Ă  adopter et les pratiques Ă  observer, la dĂ©fense choisie Ă  l’étape prĂ©cĂ©dente ayant montrĂ© quelques limitations. Nous sommes partis de l’hypothĂšse que chacun des modĂšles d’infonuagique pouvait ĂȘtre touchĂ© par ce type d’attaques, bien que de façons diffĂ©rentes. Quel que soit le modĂšle d’infonuagique, il peut en effet avoir recours Ă  des services web et se retrouve donc vulnĂ©rable d’une façon ou d’une autre, qu’il s’agisse d’un serveur web gĂ©rant toutes les requĂȘtes entrantes des utilisateurs, ou un serveur web qu’un utilisateur a lui-mĂȘme installĂ© sur une machine virtuelle qu’il loue au fournisseur. Nous avons aussi jugĂ© essentiel d’introduire les spĂ©cificitĂ©s liĂ©es Ă  l’utilisation de machines virtuelles, comme la compĂ©tition pour les ressources entre machines virtuelles situĂ©es sur une mĂȘme machine physique.----------ABSTRACT Cloud Computing is a computing paradigm that has emerged in the past few years as a very promising way of using highly scalable and adaptable computing resources, as well as accessing them from anywhere in the world and from any terminal (mobile phone, tablet, laptop...). It allows companies or individuals to use computing infrastructures without having to physically own them, and without the burden of maintenance, installations, or updates. To achieve that, Cloud Computing uses already known and tested technologies such as virtualization and web services. Several Cloud Computing models exist, divided by how much of the infrastructure the user is in charge of, ranking from nothing at all (the provider is in charge of everything, from the operating system to the applications installed) to managing a whole virtual machine without even an operating system preinstalled. For instance, sharing and accessing a document on Dropbox, or running a resource intensive application on a rented machine, are both exemples of what can be done with Cloud Computing. In the case of Dropbox, the user doesn’t care what resources are allocated for his requests, no more than he needs to know on what operating system the request was run or how the database was accessed. But all those aspects will be part of what the user has to know and adjust in the second case. A Cloud Computing network can be public, as it is the case for Amazon, which allows you to access its resources if you pay for it, or private, if a company decides to build a cluster for its own needs. The strong appeal of Cloud Computing, for both businesses and individuals, dramatically increases the security risks, because it becomes a key target for attackers. This increased risk, added to the confidence the users must have in their services provider when it comes to managing and protecting their data, may explain why many are still reluctant to take the leap to Cloud Computing. For instance, a company may be reluctant for confidentiality reasons, while individuals may hesitate for privacy concerns. The broad range of technologies used in Cloud Computing makes it at risk for a wide variety of attacks, since it already comes with all the vulnerabilities associated with any conventional network, and all the security breaches that affect virtual machines. However, those threats are usually well documented and easily prevented. But this is not the case of the vulnerabilities that come from the use of web services, that are heavily used in Cloud Computing. Cloud Computing networks aim at being accessible from all over the world and on almost any device, and that implies using web services. Yet, web services are extremely vulnerable to XML-DoS type of attack. Those attacks take advantage of Simple Object Access Protocol (SOAP) requests using a malicious XML content. Those requests can easily deplete a web server from its resources, be it CPU or memory, making it unavailable for legitimate users; this is exactly the goal of a denial-of-service attack. The XML-DoS attacks are extremely interesting in two ways. First, they are very hard to detect, since the attack takes place on the application layer, so the user appears to be legitimate (it’s impossible to detect it on the TCP/IP layer). Second, the resources needed to mount the attack are very low compared to what is needed on the web server side to process even a basic but malformed request. This type of attack has been surprisingly left quite aside, despite its efficiency and the omnipresence of web services in Cloud Computing networks. This is the reason why we decided to prove and quantify the impact such attacks can have on Cloud Computing networks, to later propose possible solutions and defenses. We estimated that using a simulated environment was the best option for various reasons, like the possibility to monitor the resources of all the servers in the network, and the greater freedom we had to build our own topology. Our first contribution is to emphasize the vulnerable equipments in a Cloud Computing network, and the various ways to attack them, as well as the various forms an XML-DoS attack can take. Our second contribution is then to use, modify and improve a Cloud Computing simulator (the GreenCloud simulator, based on NS2), in order to make the study of XML-DoS attacks possible. Once the changes are made, we show the efficiency of XML- DoS attacks, and the impact they have on legitimate users. In addition, we compare the main existing defenses against XML-DoS attacks and web services attacks in general, and pick the one that seems to be best suited to protect Cloud Computing networks. We then put this defense to the test in our simulator, to evaluate its efficiency. This evaluation must take into consideration not only the ability to mitigate the attack we led in the previous step, but also the number of false positives and false negatives. One of the major challenges is to have a defense that will conciliate the ability to protect all the machines in the network, while still being able to adapt to the great heterogeneity of the various web services hosted at the same time in a Cloud Computing network. Those experimentations are then subjected to discussions and conclusions on the decisions to take when it comes to XML-DoS attacks. In particular, what defenses should be adopted and what practices should be followed, because the evaluation of the defense at the previous step will show that it may not be the optimal solution; this will be our final contribution. We made the assumption that all the Cloud Computing models could be the target of a XML-DoS attack in some way. No matter the model, it can actually use web services and is then vulnerable to those attacks, whether it is a web server handling incoming requests for all the users, or a web server a user installed on the virtual machine he rents. We thought it was essential to take into consideration the specificity of virtual machines, such as the contention for resources when they are located on the same physical machine

    Collaborative Intrusion Detection in Federated Cloud Environments using Dempster-Shafer Theory of Evidence

    Get PDF
    Moving services to the Cloud environment is a trend that has been increasing in recent years, with a constant increase in sophistication and complexity of such services. Today, even critical infrastructure operators are considering moving their services and data to the Cloud. As Cloud computing grows in popularity, new models are deployed to further the associated benefits. Federated Clouds are one such concept, which are an alternative for companies reluctant to move their data out of house to a Cloud Service Providers (CSP) due to security and confidentiality concerns. Lack of collaboration among different components within a Cloud federation, or among CSPs, for detection or prevention of attacks is an issue. For protecting these services and data, as Cloud environments and Cloud federations are large scale, it is essential that any potential solution should scale alongside the environment adapt to the underlying infrastructure without any issues or performance implications. This thesis presents a novel architecture for collaborative intrusion detection specifically for CSPs within a Cloud federation. Our approach offers a proactive model for Cloud intrusion detection based on the distribution of responsibilities, whereby the responsibility for managing the elements of the Cloud is distributed among several monitoring nodes and brokering, utilising our Service-based collaborative intrusion detection – “Security as a Service” methodology. For collaborative intrusion detection, the Dempster-Shafer (D-S) theory of evidence is applied, executing as a fusion node with the role of collecting and fusing the information provided by the monitoring entities, taking the final decision regarding a possible attack. This type of detection and prevention helps increase resilience to attacks in the Cloud. The main novel contribution of this project is that it provides the means by which DDoS attacks are detected within a Cloud federation, so as to enable an early propagated response to block the attack. This inter-domain cooperation will offer holistic security, and add to the defence in depth. However, while the utilisation of D-S seems promising, there is an issue regarding conflicting evidences which is addressed with an extended two stage D-S fusion process. The evidence from the research strongly suggests that fusion algorithms can play a key role in autonomous decision making schemes, however our experimentation highlights areas upon which improvements are needed before fully applying to federated environments

    Theoretical and Applied Foundations for Intrusion Detection in Single and Federated Clouds

    Get PDF
    Les systĂšmes infonuagiques deviennent de plus en plus complexes, plus dynamiques et hĂ©tĂ©rogĂšnes. Un tel environnement produit souvent des donnĂ©es complexes et bruitĂ©es, empĂȘchant les systĂšmes de dĂ©tection d’intrusion (IDS) de dĂ©tecter des variantes d’attaques connues. Une seule intrusion ou une attaque dans un tel systĂšme hĂ©tĂ©rogĂšne peut se prĂ©senter sous des formes diffĂ©rentes, logiquement mais non synthĂ©tiquement similaires. Les IDS traditionnels sont incapables d’identifier ces attaques, car ils sont conçus pour des infrastructures spĂ©cifiques et limitĂ©es. Par consĂ©quent, une dĂ©tection prĂ©cise dans le nuage ne sera absolument pas identifiĂ©e. Outre le problĂšme de l’infonuagique, les cyber-attaques sont de plus en plus sophistiquĂ©es et difficiles Ă  dĂ©tecter. Il est donc extrĂȘmement compliquĂ© pour un unique IDS d’un nuage de dĂ©tecter toutes les attaques, en raison de leurs implications, et leurs connaissances limitĂ©es et insuffisantes de celles-ci. Les solutions IDS actuelles de l’infonuagique rĂ©sident dans le fait qu’elles ne tiennent pas compte des aspects dynamiques et hĂ©tĂ©rogĂšnes de l’infonuagique. En outre, elles s’appuient fondamentalement sur les connaissances et l’expĂ©rience locales pour identifier les attaques et les modĂšles existants. Cela rend le nuage vulnĂ©rable aux attaques «Zero-Day». À cette fin, nous rĂ©solvons dans cette thĂšse deux dĂ©fis associĂ©s Ă  l’IDS de l’infonuagique : la dĂ©tection des cyberattaques dans des environnements complexes, dynamiques et hĂ©tĂ©rogĂšnes, et la dĂ©tection des cyberattaques ayant des informations limitĂ©es et/ou incomplĂštes sur les intrusions et leurs consĂ©quences. Dans cette thĂšse, nous sommes intĂ©ressĂ©s aux IDS gĂ©nĂ©riques de l’infonuagique afin d’identifier les intrusions qui sont indĂ©pendantes de l’infrastructure utilisĂ©e. Par consĂ©quent, Ă  chaque fois qu’un pressentiment d’attaque est identifiĂ©, le systĂšme de dĂ©tection d’intrusion doit ĂȘtre capable de reconnaĂźtre toutes les variantes d’une telle attaque, quelle que soit l’infrastructure utilisĂ©e. De plus, les IDS de l’infonuagique coopĂšrent et Ă©changent des informations afin de faire bĂ©nĂ©ficier chacun des expertises des autres, pour identifier des modĂšles d’attaques inconnues.----------ABSTRACT: Cloud Computing systems are becoming more and more complex, dynamic and heterogeneous. Such an environment frequently produces complex and noisy data that make Intrusion Detection Systems (IDSs) unable to detect unknown variants of known attacks. A single intrusion or an attack in such a heterogeneous system could take various forms that are logically but not synthetically similar. This, in turn, makes traditional IDSs unable to identify these attacks, since they are designed for specific and limited infrastructures. Therefore, the accuracy of the detection in the cloud will be very negatively affected. In addition to the problem of the cloud computing environment, cyber attacks are getting more sophisticated and harder to detect. Thus, it is becoming increasingly difficult for a single cloud-based IDS to detect all attacks, because of limited and incomplete knowledge about attacks and implications. The problem of the existing cloud-based IDS solutions is that they overlook the dynamic and changing nature of the cloud. Moreover, they are fundamentally based on the local knowledge and experience to perform the classification of attacks and normal patterns. This renders the cloud vulnerable to “Zero-Day” attacks. To this end, we address throughout this thesis two challenges associated with the cloud-based IDS which are: the detection of cyber attacks under complex, dynamic and heterogeneous environments; and the detection of cyber attacks under limited and/or incomplete information about intrusions and implications. We are interested in this thesis in allowing cloud-based IDSs to be generic, in order to identify intrusions regardless of the infrastructure used. Therefore, whenever an intrusion has been identified, an IDS should be able to recognize all the different structures of such an attack, regardless of the infrastructure that is being used. Moreover, we are interested in allowing cloud-based IDSs to cooperate and share knowledge with each other, in order to make them benefit from each other’s expertise to cover unknown attack patterns. The originality of this thesis lies within two aspects: 1) the design of a generic cloud-based IDS that allows the detection under changing and heterogeneous environments and 2) the design of a multi-cloud cooperative IDS that ensures trustworthiness, fairness and sustainability. By trustworthiness, we mean that the cloud-based IDS should be able to ensure that it will consult, cooperate and share knowledge with trusted parties (i.e., cloud-based IDSs). By fairness, we mean that the cloud-based IDS should be able to guarantee that mutual benefits will be achieved through minimising the chance of cooperating with selfish IDSs. This is useful to give IDSs the motivation to participate in the community
    corecore