This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Belgium"

From OWASP
Jump to: navigation, search
(-)
(Structural Sponsors 2017)
Line 43: Line 43:
  
 
= Chapter Meetings  =
 
= Chapter Meetings  =
 +
 +
== Upcoming Meeting (29 May 2017) in Diegem ==
 +
 +
=== WHEN ===
 +
Tuesday 29 May 2017
 +
 +
=== WHERE  ===
 +
Hosted by .
 +
 +
Address: <br>
 +
 +
=== PROGRAM ===
 +
The agenda:
 +
*18h00 - 19h00: '''Welcome & sandwiches'''<br>
 +
*19h00 - 19h10: '''[https://www.owasp.org/images/2/24/Owasp_Belgium_update_2017-02-28.pdf OWASP Update]''' (by Lieven Desmet)<br>
 +
*19h10 - 20h00: '''HTTP for the worst and the best''' (by Xavier Mertens, freelance security consultant)<br>
 +
:''Abstract:''  Today, the classic infection vectors remain SMTP and HTTP. Many spam & phishing campaigns are delivered to the victim’s mailbox and usually the next step of the attack is performed on top of HTTP, by visiting a malicious website or downloading a piece of malicious code. This talk will be split in two parts. To begin, I’ll explain how HTTP techniques are used to make the life of security researchers and incident handlers more difficult (attackers use many techniques to prevent access to their juicy data). The next part will demonstrate that attackers are also humans and make mistakes like all of us. They also need to follow the OWASP Top-10! I’ll review some example of bad code / bad configuration that I found during my investigations.
 +
:''Bio:'' '''Xavier Mertens''' is a freelance security consultant based in Belgium. His job focuses on protecting his customers by applying “offensive” (pentesting) as well as “defensive” security (incident handling, log management, SIEM, security visualisation, OSINT). Xavier is also a SANS Internet Storm Center handler (<nowiki>https://isc.sans.org</nowiki>). He’s also maintaining his security blog (<nowiki>https://blog.rootshell.be</nowiki>) and is a co-organizer of the BruCON security conference (<nowiki>http://www.brucon.org</nowiki>).<br>
 +
*20h10 - 21h00: '''[https://www.owasp.org/images/d/db/DeRyck_OWASP_WebSecurityOverview_2017-02-28.pdf Why traditional Web security technologies no longer suffice]''' (by Philippe De Ryck, KU Leuven)<br>
 +
:''Abstract:'' Not a day goes by without a story on a Web security incident somewhere. A data breach disclosing millions of people’s details. A defacement of a major Web site. Malware served from a legitimate Web site to thousands of users. Contrary to popular belief, the people running these Web sites are generally not clueless about security, but getting it right is just not that easy. Recent evolutions, like the rise of public networks, or the strong dependence on third-party code, have made it easier to attack Web sites, and harder to defend them. Join us to get an overview of these threats, and to take a dive into HTTP Strict Transport Security (HSTS), one of the latest Web security technologies that really help you improve security.
 +
:''Bio:'' '''Philippe De Ryck''' is a professional speaker and trainer on software security and web security. Since he obtained his PhD at the imec-DistriNet research group (KU Leuven, Belgium), he has been running the group's Web Security Training program, which ensures a sustainable knowledge transfer of the group’s security expertise towards practitioners.
 +
:20h00 - 20h10: '''Reception'''
 +
 +
=== REGISTRATION  ===
 +
Please register via EventBrite: https://owasp-belgium-2017-02-28.eventbrite.com
 +
 +
=== Coverage ===
  
 
== Upcoming Meeting (28 February 2017) in Leuven ==
 
== Upcoming Meeting (28 February 2017) in Leuven ==
Line 84: Line 111:
 
Hosted at [http://www.ugent.be/ UGent]
 
Hosted at [http://www.ugent.be/ UGent]
  
Faculteit Ingenieurswetenschappen en Architectuur<br/>
+
Faculteit Ingenieurswetenschappen en Architectuur<br />
Campus Boekentoren<br/>
+
Campus Boekentoren<br />
Jozef Plateaustraat 22<br/>
+
Jozef Plateaustraat 22<br />
9000 Gent<br/>
+
9000 Gent<br />
Belgium<br/>
+
Belgium<br />
  
 
=== PROGRAM ===
 
=== PROGRAM ===
 
The agenda:
 
The agenda:
 
*18h15 - 19h00: '''Welcome & sandwiches'''<br>  
 
*18h15 - 19h00: '''Welcome & sandwiches'''<br>  
*19h00 - 19h10: '''[https://www.owasp.org/images/1/1c/Owasp_Belgium_update_2016-10-18_v1.pptx OWASP Update]  <br>  
+
*19h00 - 19h10: '''[https://www.owasp.org/images/1/1c/Owasp_Belgium_update_2016-10-18_v1.pptx OWASP Update]  <br> '''
 
*19h15 - 19h45: '''[https://www.owasp.org/images/7/73/Presentation_Sensei_Security_v17_for_distribution.pdf Find and fix software security problems… wait, do not make security mistakes in the first place!]''' (by Matias Madou)<br>
 
*19h15 - 19h45: '''[https://www.owasp.org/images/7/73/Presentation_Sensei_Security_v17_for_distribution.pdf Find and fix software security problems… wait, do not make security mistakes in the first place!]''' (by Matias Madou)<br>
 
:''Abstract:'' Today, companies do not have a shortage of known security problems in their solutions. Tools and people point out numerous software security problems that eventually should be fixed. So how do organizations deal with all these issues? What is the most effective way to get issues fixed? For companies taking security serious, the question is no longer “How many problems can you find?”, but the real question is “How many security issues can you fix or prevent developers from making?” In this session, we explore different routes on how to find and fix security issues, or prevent making them in the first place.
 
:''Abstract:'' Today, companies do not have a shortage of known security problems in their solutions. Tools and people point out numerous software security problems that eventually should be fixed. So how do organizations deal with all these issues? What is the most effective way to get issues fixed? For companies taking security serious, the question is no longer “How many problems can you find?”, but the real question is “How many security issues can you fix or prevent developers from making?” In this session, we explore different routes on how to find and fix security issues, or prevent making them in the first place.
Line 120: Line 147:
 
Hosted at [http://www.pwc.be PwC]
 
Hosted at [http://www.pwc.be PwC]
  
Woluwedal 18<br/>
+
Woluwedal 18<br />
1932 Zaventem<br/>
+
1932 Zaventem<br />
Belgium<br/>
+
Belgium<br />
  
 
Google Maps: https://goo.gl/maps/3Jo8u
 
Google Maps: https://goo.gl/maps/3Jo8u
Line 131: Line 158:
 
The agenda:
 
The agenda:
 
*18h15 - 19h00: '''Welcome & sandwiches'''<br>  
 
*18h15 - 19h00: '''Welcome & sandwiches'''<br>  
*19h00 - 19h15: '''OWASP Update  <br>  
+
*19h00 - 19h15: '''OWASP Update  <br> '''
 
*19h15 - 20h00: '''[https://www.owasp.org/images/0/0e/CloudPiercerOwasp_20160908.pdf CloudPiercer: Bypassing Cloud-based Security Providers]''' (by Thomas Vissers, iMinds-DistriNet-KU Leuven)<br>
 
*19h15 - 20h00: '''[https://www.owasp.org/images/0/0e/CloudPiercerOwasp_20160908.pdf CloudPiercer: Bypassing Cloud-based Security Providers]''' (by Thomas Vissers, iMinds-DistriNet-KU Leuven)<br>
 
:''Abstract:'' Many website owners turn to Cloud-based Security Providers (CBSPs) to protect their websites from DDoS and web application attacks. Some of these security services rely solely on changing the DNS settings of a customer’s domain name to reroute his traffic through the CBSP's cloud infrastructure. This allows for complete circumvention of the security service by directly attacking the website’s hosting IP address. Therefore, it is crucial that a web server's hosting IP address remains hidden from potential attackers. Despite this risk, our study has shown that, in practice, over 70% of CBSP-protected domains are exposing their real IP address. In this talk, we will discuss several significant attack vectors and steps administrators can take to prevent their IP address from being discovered by attackers.
 
:''Abstract:'' Many website owners turn to Cloud-based Security Providers (CBSPs) to protect their websites from DDoS and web application attacks. Some of these security services rely solely on changing the DNS settings of a customer’s domain name to reroute his traffic through the CBSP's cloud infrastructure. This allows for complete circumvention of the security service by directly attacking the website’s hosting IP address. Therefore, it is crucial that a web server's hosting IP address remains hidden from potential attackers. Despite this risk, our study has shown that, in practice, over 70% of CBSP-protected domains are exposing their real IP address. In this talk, we will discuss several significant attack vectors and steps administrators can take to prevent their IP address from being discovered by attackers.
Line 166: Line 193:
 
The agenda:
 
The agenda:
 
*18h00 - 19h00: '''Welcome & sandwiches'''<br>  
 
*18h00 - 19h00: '''Welcome & sandwiches'''<br>  
*19h00 - 19h10: '''OWASP Update  <br>  
+
*19h00 - 19h10: '''OWASP Update  <br> '''
 
*19h10 - 20h00: '''All Your Biases Belong to Us: Breaking RC4 in WPA-TKIP and TLS''' (by Mathy Vanhoef, iMinds-DistriNet-KU Leuven)<br>
 
*19h10 - 20h00: '''All Your Biases Belong to Us: Breaking RC4 in WPA-TKIP and TLS''' (by Mathy Vanhoef, iMinds-DistriNet-KU Leuven)<br>
 
:''Abstract:'' We present new biases in RC4, break the Wi-Fi Protected Access Temporal Key Integrity Protocol (WPA-TKIP), and design a practical plaintext recovery attack against the Transport Layer Security (TLS) protocol. To empirically find new biases in the RC4 keystream we use statistical hypothesis tests. This reveals many new biases in the initial keystream bytes, as well as several new long-term biases. Our fixed-plaintext recovery algorithms are capable of using multiple types of biases, and return a list of plaintext candidates in decreasing likelihood.
 
:''Abstract:'' We present new biases in RC4, break the Wi-Fi Protected Access Temporal Key Integrity Protocol (WPA-TKIP), and design a practical plaintext recovery attack against the Transport Layer Security (TLS) protocol. To empirically find new biases in the RC4 keystream we use statistical hypothesis tests. This reveals many new biases in the initial keystream bytes, as well as several new long-term biases. Our fixed-plaintext recovery algorithms are capable of using multiple types of biases, and return a list of plaintext candidates in decreasing likelihood.
Line 213: Line 240:
  
 
=== Coverage ===
 
=== Coverage ===
 
  
  
Line 241: Line 267:
 
*David Mathy, Freelance
 
*David Mathy, Freelance
  
Our goal is to professionalize the local OWASP functioning, provide in a bigger footprint to detect OWASP opportunities such as speakers/topics/sponsors/… and set a 5 year target on: Target audiences, Different events and Interactions of OWASP global – local projects. __NOTOC__ <headertabs/>
+
Our goal is to professionalize the local OWASP functioning, provide in a bigger footprint to detect OWASP opportunities such as speakers/topics/sponsors/… and set a 5 year target on: Target audiences, Different events and Interactions of OWASP global – local projects.  
 +
__NOTOC__ <headertabs></headertabs>
 
[[Category:Europe]]
 
[[Category:Europe]]

Revision as of 19:31, 19 April 2017

OWASP Belgium

Welcome to the Belgium chapter homepage. The chapter leader is Sebastien Deleersnyder


Participation

OWASP Foundation (Overview Slides) is a professional association of global members and is open to anyone interested in learning more about software security. Local chapters are run independently and guided by the Chapter_Leader_Handbook. As a 501(c)(3) non-profit professional association your support and sponsorship of any meeting venue and/or refreshments is tax-deductible. Financial contributions should only be made online using the authorized online chapter donation button. To be a SPEAKER at ANY OWASP Chapter in the world simply review the speaker agreement and then contact the local chapter leader with details of what OWASP PROJECT, independent research or related software security topic you would like to present on.

Sponsorship/Membership

Btn donate SM.gif to this chapter or become a local chapter supporter. Or consider the value of Individual, Corporate, or Academic Supporter membership. Ready to become a member? Join Now BlueIcon.JPG


Upcoming events

Upcoming chapter meetings

We will organize our next chapter meetings in 2017:

See https://www.owasp.org/index.php/Belgium#Chapter_Meetings for more details.

Stay in touch

Meetup-logo-2x.png Join the list.png Follow-us-on-twitter.png Linkedin-button.gif

If you want to be invited for the next OWASP Belgium Chapter meetings, please drop us your contact info.

Structural Sponsors 2017

OWASP Belgium thanks its structural chapter supporters for 2017 and the OWASP BeNeLux Days 2016:

VeraCode logo.png Vest.jpg Intigriti verticaal.jpg Ecurify-2016.png HPE logo 250.png LogoToreon.jpg Zionsecurity.jpg Nviso logo RGB baseline 200px.png Whitehat-security hor.jpg

If you want to support our chapter, please contact Seba Deleersnyder