Getting to know what’s going on is a primary goal of information security. There is even a name for it: intrusion detection. And there are tools to do this. That’s the easy part. Once you have decided you want intrusion detection or intrusion prevention, the implementation part becomes a lot more difficult. Well, if you need help with this issue, there is a two-day workshop for you at DeepSec 2014 – the Suricata Training Event.
Suricata is a high performance Network Intrusion Detection System (IDS), Intrusion Prevention System (IPS) and Network Security Monitoring engine. It can serve pretty much all your needs. It’s Open Source (so it cannot be bought and removed from the market) and owned by a very active community. Suricata is managed by the non-profit foundation; the Open Information Security Foundation (OISF). OISF’s mission is to remain on the leading edge of open source IDS/IPS development to meet the ongoing needs of the community.
The two-day training event is held by core developers of Suricata. This means you get all the information on how intrusion detection works, how the rules can be created and adapted to your needs straight from the experts. Attending the workshop will give you not only a greater proficiency in Suricata’s core technology but will also have the unique opportunity to bring questions, challenges, and new ideas directly to Suricata’s developers. You will get the theory plus hands-on exercises with live packets and detection signatures. A sample of topics that will be covered over the course of the 2-day training include:
If you own or use a network, then you should definitely be interested in IDS/IPS – get the packets before the packets get you! The workshop is tailored for developers, technologists, and security professionals. Even if you are new to Suricata or IDS in general, the training is a perfect starting point to get familiar with the topic. Make sure to book early, the number of tickets for all workshops is limited!
Backdoors are devious. Usually you have to look for them since someone has hidden or „forgotten“ them. Plus backdoors are very fashionable these days. You should definitely get one or more. Software is (very) easy to inspect for any rear entrances. Even if you don’t have access to the source code, you can deconstruct the bytes and eventually look for suspicious parts of the code. When it comes to hardware, things might get complicated. Accessing code stored in hardware can be complex. Besides it isn’t always clear which one of the little black chips holds the real code you are looking for. Since all of our devices we use every days runs on little black chips (the colour doesn’t matter, really), everyone with trust issues should make sure that control of these devices is in the right hands – or bytes.
DeepSec 2014 features a talk where BIOS-based hypervisors are discussed. There is ongoing research on this topic. Getting control of a computer’s BIOS or any other part of crucial firmware allows adversaries to either control or at least watch the code a machine is running. Imagine your firmware having an extra layer of virtualisation technology. Usually this is undesirable, especially if an unknown third party is accessing this layer. We asked a well-known Information Security Specialist to present the state of the research regarding these extra features in hardware. The talk will also introduce means to detect hidden hypervisors in firmware and give examples where these modifications were found in the wild. Once attackers go to extra sneaky on the stealth scale, you don’t always get the luxury of detecting backchannel activity. Aliens don’t always phone home, unfortunately.
Everyone using black boxes and computer chips should attend this talk. We know that avoiding unknown firmware and chip designs is hard (hence the term hardware), but you should pay attention to unauthorised modifications of these components. This is crucial if you use the hardware for your own (or someone else’s) infrastructure.
Keep in mind: The materials of this presentation have not been published before, and the research covers a period of more than a year. Drop by and raise your paranoia level! ☺
If you haven’t been at 44CON last week, you missed a lot of good presentations. Plus you haven’t been around great speakers, an excellent crew, “gin o’clock” each day, wonderful audience, and great coffee from ANTIPØDE (where you should go when in London and in desperate need of good coffee).
Everyone occasionally using wireless connections (regardless if Wi-Fi or mobile phone networks) should watch the talks on GreedyBTS and the improvements of doing Wi-Fi penetration testing by using
fake alternative access points. GreedyBTS is a base transceiver station (BTS) enabling 2G/2.5G attacks by impersonating a BTS. Hacker Fantastic explained the theoretical background and demonstrated what a BTS-in-the-middle can do to Internet traffic of mobile phones. Intercepting and re-routing text messages and voice calls can be done, too. Implementing the detection of fake base stations is now a very good idea. Some specialised phones do this already. Recently an Austrian research team has published work on detecting interception equipment. Unless you use additional security mechanisms you should take a look at these technologies. Doesn’t hurt if you about it any way.
Hacking Wi-Fi got a serious boost by a presentation from Dominic White. The title was Manna from Heaven; Improving the state of wireless rogue AP attacks, and it showed the state of affairs of modern Wi-Fi hardware. Vendors have tried to defend against the attacks of the past. Especially when it comes to stripping SSL things such as the hard-coded root certificates in Google’s web browser make the life of a pen-tester hard. The updated toolbox called mana will help you to deal with modern Wi-Fi clients. Everyone using wireless communication should now about the risks involved. When in doubt, always remember that connecting to a wireless network acts as a strong form of exposure.
Conan Dooley talked about the challenges of running a network infrastructure at a hacker conference. Once you deal with very talented and creative people, then off-the-shelf solutions might not be the way to go. He offered very useful insights into the operation and gave helpful hints for anyone having to deal with a similar challenge. If it works for a hacker con, it will probably do some good for your enterprise network.
Joxean Koret demonstrated how to break the detection of malware by anti-virus. His examples shed light on the quality of the software. A lot of anti-virus products disable the protection mechanisms of the operating system in order to perform tests. This can lead to exposing the system to attack code in the worst case (paradoxically enabling malicious code to exploit the anti-virus software to gain a foothold). Again anti-virus filters aren’t the magical solution to malware entering your network. Joxean did a very good job showing this, and we recommend looking at the examples he gave in his presentation.
Speaking of incidents, you should think about them in advance. Steve Armstrong spoke about beginner’s incident handling mistakes and how to avoid them. Investigating the trails of attackers and throwing them out of your network/hosts is a task that relies on a lot more than technology. Step by step Steve explained the core failures and concepts. In addition he presented a tool called CyberCPR which enables response teams to collaborate and securely exchange information about a case. It’s still in its beta stage, but we suggest to give it a try.
We definitely look forward to attend 44CON next year! See you 8-11 September 2015 in London!
Filtering inbound and outbound data is most certainly a part of your information security infrastructure. A prominent component are anti-virus content filters. Your desktop clients probably have one. Your emails will be first read by these filters. While techniques like this have been around for a long time, they regularly draw criticism. According to some opinions the concept of anti-virus is dead. Nevertheless it’s still a major building block of security architecture. The choice can be hard, though. DeepSec 2014 features a talk by Daniel Sauder, giving you an idea why anti-virus software can fail.
Someone who is starting to think about anti-virus evasion will see, that this can be reached easy (see for example last year’s DeepSec talk by Attila Marosi). If an attacker wants to hide a binary executable file with a Metasploit payload, the main points for accomplish this goal is mainly
By developing further evasion techniques it is possible to research the internal functionality of anti-virus products. For example it can be determined whether a product is using x86 emulation or not, and what the emulation is capable of, and which Microsoft Windows API calls can disturb the anti-virus engine itself. Other tests include building an .exe file without a payload generated with msfpayload and well known attacking tools as well as 64-bit payloads and escaping techniques.
At the time of this writing Daniel Sauder developed 36 different techniques as proof of concept code and tested them against 8 different anti-virus products. More techniques and engines are pending. Together with documentation, papers, and talks from other researchers, this gives a deeper understanding for the functionality of anti-virus software and shows, where it is failing generally and in particular.
Anti-virus software is no magic solution that will always perfectly work. If you run filters of this kind, we recommend attending Daniel’s talk. Once you know how your defence mechanisms fail, you can work to improve them.
Modern environments feature a lot of platforms that can execute code by a variety of frameworks. There are UNIX® shells, lots of interpreted languages, macros of all kinds (Office applications or otherwise), and there is the Microsoft Windows PowerShell. Once you find a client, you usually will find a suitable scripting engine. This is very important for defending networks and – of course – attacking them. Nikhil Mittal will present ways to use the PowerShell in order to attack networks from the inside via the exploitation of clients.
PowerShell is the “official” shell and scripting language for Windows. It is installed by default on all post-Vista Windows systems and is found even on XP and Windows 2003 machines in an enterprise network. Built on the .NET framework, PowerShell allows interaction with almost everything one finds in a Windows machine and network. One could access system registry, Windows API, WMI, COM objects, .NET libraries, access other machines on network and so on. It is very useful for system administrators which make it an ideal tool/platform for penetration testers as well.
PowerShell has various distinct advantages over binaries and other non-Windows scripting languages. It is trusted by the operating system, the system administrators and antivirus. It is possible to perform various attacks using PowerShell without dropping anything to the disk. Add to this, the ability to natively interact with the machine and the network and you have a tool for penetration tests which is too good to be true!
There has been much interesting work on usage of PowerShell in penetration tests. The talk will introduce Nishang, which is a toolkit for usage of PowerShell in penetration tests. It has scripts divided under following heads:
One frequently asked question by users of Nishang is this: How PowerShell could be used for getting access to a network? Could it be used for getting a foothold in an enterprise network? Yes, of course, use client side attacks.
In this presentation it will be demonstrated that a client side attack with PowerShell is very effective as it exploits human ignorance and uses features of PowerShell – both inherent to any enterprise network. The attacks demonstrated would be phishing (user clicks on a link), malicious attachments (MS Word and Excel), malicious shortcuts (.LNK file), attacks using Java applets and Human Interface Devices (HIDs).
There have been many instances of PowerShell being used by malware writers for client side attacks. Some notable examples, a Russian ransomware, for infecting MS Office files, and malicious short-cuts.
The PowerShell scripts that will be presented in this talk draw inspiration from some of the above attacks.
This talk should be attended by those who do external penetration tests and would like to know more about using PowerShell for this purpose. System Administrators should also attend this talk to understand the latest tools used by the attackers.
For anyone intending to dive deeper into the powers of the PowerShell, we strongly recommend booking Nikhils training course, also held at DeepSec 2014.
The „Cloud“ technology has been in the news recently. No matter if you use „The Cloud™“ or any other technology for outsourcing data, processes and computing, you probably don’t want to forget about trust issues. Scattering all your documents across the Internet doesn’t require a „Cloud“ provider (you only need to click on that email with the lottery winnings). Outsourcing any part of your information technology sadly requires a trust relationship. How do you solve this problem? Armin Simma of the Vorarlberg University of Applied Sciences has some ideas and will present them at DeepSec 2014.
Th presentation shows a combination of technologies on how to make clouds trustworthy. One of the top inhibitors for not moving (virtual machines) to the cloud is security. Cloud customers do not fully trust cloud providers. The problem with sending virtual machines to the cloud is that „traditional“ encryption is no solution because encrypted data (equal to code in our case) can not be executed. Taking a closer look at the numerous surveys about cloud adoption (and at inhibitors for not moving to the cloud) it can be seen that insider attacks are ranked in the top critical attacks. The insider in our scenario is the administrator (or a user with high/elevated privileges).
The key point is: the cloud customer is not trusting the administrator of the cloud provider’s system.
The solution to this problem is based on
Mandatory Access Control is used to prevent the administrator – who must be able to administer and thus access the host system – from accessing Virtual Machines running on top of the cloud provider’s system(s). Our system is able to log all activities of users. Users (including the administrator himself/herself) are not able to manipulate this log.
The former technology – Trusted Computing – is used as a mechanism for giving the cloud customer a proof that the system hosting his Virtual Machines (= the cloud provider’s infrastructure) was not manipulated. The proof is hardware-based: it prevents several kinds of attacks e.g. rootkits or other BIOS-manipulating attacks. The proof is based on measuring all systems (system parts) which were executed since boot time of the physical machine. Each part is measured before execution. This „measurement chain“ is called Trusted Boot. A standardised tamper-resistant hardware (the TPM) plus a standardized protocol allows for the proof to the customer. The proof is called attestation.
A second technology used for securing the cloud is Trusted Computing’s sealing mechanism. Sealing is an extension of asymmetric encryption: the decryption is done within the hardware (TPM) but only if the current measurement values are equal to predefined reference values. The reference values are defined by the cloud customer and specify a known good system plus system configuration . These techniques (Trusted Boot, Attestation, Sealing) allow the cloud customer to be sure that a specific (trustworthy) system is running on the provider’s site.
Armin’s talk is of interested to implementers and users of „Cloud“ infrastructure alike. In case you are playing with Trusted Computing, you should attend his talk as well.
All good defences start with some good ideas. The is also true for information security. DeepSec 2014 features a presentation by Vlado Luknar who will give you decent hints and a guideline on how to approach the dreaded risk assessment with readily available tools. We have kindly asked Vlado to give you a detailed teaser on what to expect:
It seems fairly obvious that every discussion about information security starts with a risk assessment. Otherwise, how do we know what needs to be protected, how much effort and resources we should put into preventing security incidents and potential business disasters? With limited time and budget at hand we’d better know very well where to look first and what matters the most.
If we look at some opinion-making bodies in information security, such as ISF, ISACA or (ISC)², and of course, at ISO/IEC standards (the 27000 series), we can see that in information security there is no escape from risk assessment. A difficult question for anyone responsible for managing information security is to decide when to rely on best practice or baseline security controls and when to apply risk assessment and in what detail.
Risk assessment in information security is, at least in theory, quite self-evident. We have to
In the end, we arrive at our risk R by calculating impact times probability (I×P), almost certainly identifying some actions to perform (i.e. measures to mitigate the risk, either its impact or probability).
Well, that’s the easy part. Now, we are supposed to repeat this risk assessment- either as soon as any of these variables changes (objective, asset, system, threat, vulnerability, control) or at least once per agreed-on period of time.
In general, existing security compliance frameworks (e.g. ISO/IEC 27001, COBIT, PCI DSS) do not dictate any specific risk assessment methodologies or tools. The common agreement seems to be: stick to the scheme of asset-threat-vulnerability-control and use whatever suits you to objectively reduce risks – anything that allows you to be consistent, reproducible and measurable.
And this is the moment you start looking for a risk assessment tool, be it a commercial or an open-source one. In fact, your security team may be small and you may have no risk assessment specialist in there. Yet, you need to be structured about your security risk decisions in a easy-to-do and efficient manner every time you run an assessment hoping that if you don’t catch something important in this run, you will succeed in the next iteration, or an incident will teach you about it the hard way.
How many risk assessment methodologies for information security can we find on Internet today? If you filter out government- and consultancy-related methodologies (mostly without a tangible product you could buy) you end up with a list of 15-20 different methodologies with some of them comprising also a risk assessment tool. This might seem like a lot but only until you try to implement one of them in your organization.
You start with the first one and realize it needs weeks of training because its learning curve is so steep, the other uses awkward terminology, the next one has some strange threat categories mixing apples with oranges or uses just plain old references (talking about Windows 95, fax machines and dial-up connections) and another one requires you to take a series of complicated installation and configuration steps (plus requiring a highly privileged account on your desktop). And yet another group of tools, instead of risk assessment, talks about scanning and vulnerability management.
In fact, if you are a security manager in a small to medium size company where every security topic passes through your hands, you might be better off by using your own tool because building it is not a rocket science and does not take that much time. You develop its features on the go and by doing it you capture all the internal knowledge that otherwise might be lost.
Over the years of being a security practitioner in a commercial organization I have learned few things.
The presentation is not about latest advances in information security risk assessment. It will describe the process of making a practical, wiki-based tool, starting with publicly available resources: threats, vulnerabilities and controls (mostly from ISO/IEC 2700X) that are merged into a light ecosystem that is configured, improved and used only via a web browser. Such an ecosystem, actually an Information Security Management System called RISSCON, is used daily in a real company (Orange Slovensko a.s.) to keep up with the requirements of ISO/IEC 27001.
In case you haven’t noticed, the Internet is getting crowded. Next to having billions of people online, their devices are starting to follow. Information security experts can’t wait to see this happen. The future relies on the Internet Protocol Version 6 (IPv6). IPv6 features a lot of improvements over IPv4. Since you cannot get complex stuff right at the first time, IPv6 brings some security implications with it. Past and present conferences have talked about this. DeepSec 2014 is no exception. Enno Rey of ERNW will talk about Multicast Listener Discovery (MLD) in his presentation.
The presentation is the first time that the results of an ongoing research of MLD are published. MLD is a protocol belonging to the IPv6 family, and sadly it features insecurities. MLD (Multicast Listener Discovery), and its successor, MLDv2, are used by IPv6 routers for discovering multicast listeners on a directly attached link, much like the Internet Group Management Protocol (IGMP) is used in IPv4. Even if you haven’t realised it yet, MLD is already everywhere. Many multicast applications, when the underlying layer-3 protocol is IPv6, base their operation on MLD, while most of the modern Operating Systems (OS), like Windows, Linux and FreeBSD, not only come pre-configured with IPv6 enabled, but they also start-up by sending MLD traffic, which is repeated periodically. Despite of the out-of-the-box usage of MLD, it is one of the IPv6 protocols that have not be studied yet to a suitable extend, especially as far as its potential security implications are concerned. As it will be shown, these can vary from OS fingerprinting on the local-link by sniffing the wire passively, to amplified Denial of Service attacks.
Specifically, in this talk, after presenting the results of the analysis of the default behaviour of some of the most popular OS, we will examine, by using specialised tools, whether the specific OS implementations conform to the security measures defined by the corresponding RFCs, and if not, what are the potential security implications. Then, by diving into the specifications of the protocol, we will discuss potential security issues related with the design of MLD and how they can be exploited by attackers. Finally, specific security mitigation techniques will be proposed to defend against them, which will allow us to secure IPv6 networks to the best possible extend in the emerging IPv6 era.
Let’s make the IPv6 world a safer place! ☻
For anyone dealing with IPv6, DeepSec 2014 also offers a two day training IPv6 Attacks and Defenses – A Hands-on Workshop, held by Enno himself.
Internet service providers already rolled out IPv6, especially for hosted or co-located environments. Furthermore IPv6 connectivity is widely available by means of tunnels (Teredo for example). This is why we recommend Enno’s talk and training for anyone using networks (Internet connection is optional since most operating systems use IPv6 locally any way). Deal with your network before attackers do!
It’s good if your organisation has someone to take on information security. However it’s bad if you are the person in this position. Few are lucky enough to actually deal with improving information security. And some are caught in compliance fighting an uphill struggle against regulations and audits that have nothing to do with the threats to your business.
The management of Information Security has become over-regulated and to some degree, over-focused on compliance to policy/regulation, architectural decisions, network access, and vulnerability management. As a result, many CISOs struggle to define success in terms that match the goals of their business, and struggle to make their risk management efforts relevant to senior executives.
How do you achieve that? Alex Hutton will tell you in his keynote talk at DeepSec 2014. His goal is for attendees to walk away after the talk with two things. First, a technique they can take back to their jobs with them that will help them make the concept of “aligning security with the business” less of a platitude and more of a reality. Second, we will discuss a new, threat-centric framework that uses metrics to understand how security operations reduces risk.
Curious? Cursed with being a CSO? Dreaming to become one someday? Having nightmares about metrics? Well, then you should probably avoid missing Alex’ keynote!
Microtrash37 of the EuroTrashSecurity podcast is out! We had a little talk with Chris about the schedule of DeepSec 2014 and what to expect. It’s a teaser for the blog articles about the talks and the trainings to come. We will describe more details on the blog, but you get a good overview what to expect from the audio.
We also got some inside information on the upcoming BSidesVienna 0x7DE. We will definitely attend and so should you! The BSidesVienna has some cool surprises for you. Don’t miss out on the chance to get together. The Call for Papers is still open! If you have something to share, please consider submitting a talk.
BSidesVienna was started in 2011. There were some smaller BSides-like events in Vienna in the past two years. BSidesVienna 2014 is planned for the 22 November 2014 (right after DeepSec 2014). The call for papers will close on 30 September 2014, so if you have interesting stuff you want to show onstage, then submit it to the BSidesVienna team.
You can’t keep a good con down… so let’s have fun and infosec talks at BSidesVienna 2014!
After weeks of hard work we have now the preliminary schedule of DeepSec 2014 online! We received over hundred submissions, and we had to navigate through a lot of publications, abstracts and references. We hope that you like the mixture of topics. We especially hope that you will find the offered trainings interesting.
We still wait for content and corrections, so bear with us while the schedule takes its final form. Contrary to the past years we had a lot more to do in terms of completing information about submitted talks and trainings. We will tell you more about this in the upcoming blog articles (which we will announce on our Twitter account, so you don’t miss anything).
Looking forward to see you in Vienna in November!
The Call for Papers of DeepSec 2014 officially ended yesterday. We are currently reviewing all your submissions and will publish the preliminary schedule in the course of the next two weeks. As always, you did a very good job of finding things to break and to exploit. Our choice what to include in the schedule will be pretty hard!
For those who still have bright ideas and no time to submit, please send us your abstracts as soon as possible! We will consider everything submitted so far first, but we will take your proposals into account. You just need to tell us.
The Call for Papers of DeepSec 2014 is still open. Since its motto is the power of knowledge we address everyone having knowledge. Information is the „cyber“ weapon of the 21rst century, we have heard. So if you know about the 0day that affects half the Internet, you should definitely think about presenting it at DeepSec 2014. ☻
Seriously, we have chosen this motto, because a lot of issues in information security deal with knowledge. If your IT staff knows about the latest threats, the capabilities of the defences, the state of the systems, and how to deal with problems, then you have a distinct advantage. Not knowing is usually the first step of running into problems. In this tradition we prefer disclosure of security-related knowledge. The dreaded CVE-2014-0160 is a good example. Imagine OpenSSL deployments still had the Heartbleed bug (which some of them still do, sadly) and no one knew about this. Ignorance isn’t always bliss. Disclosing this information will eventually render offensive tools ineffective. This was discussed by fx in his keynote for DeepSec 2012.
The submissions we received so far look very promising. Can you think of ways how knowledge can affect information security for better or worse? We bet you can, so let us know.