Difference between revisions of "Netherlands"

Revision as of 11:51, 21 November 2008

OWASP Netherlands

Welcome to the Netherlands chapter homepage. The chapter leader is Bert Koelewijn <paypal>Netherlands</paypal>

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

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?

Meeting schedule 2008

This is an overview of the 2008 local chapter meeting schedule. Details of the meetings can be found in the announcements that will be posted below this schedule.

March 26th
----------
Time         : 17.30 - 21.30
Main Topic   : Software Vulnerability assessment
Presentations: Complex(ity) matters, Mario de Boer (Dutch)
               V.A.C. SQL injection, Marinus Kuivenhoven (Dutch)
               Secure Programming with Static Analysis, Brian Chess (English) 
Location     : Mercure Utrecht Nieuwegein, Buizerdlaan 10, 3435 SB Nieuwegein
Sponsor      : Fortify Software

Oktober 27th
----------
Time         : 17.30 - 21.30
Main Topic   : Privacy and the Internet
Presentations: Privacy and Internet (Dutch), Frank Fruijthoff and Ellen Hoving
               Vulnerability and source code scanners. (Dutch) Emile Strijbos 
Location     : ps_testware B.V., Dorpsstraat 26, 3941 JM DOORN
Sponsor      : ps_testware B.V.

December 11th
----------
Time         : 17.30 - 21.30
Main Topic   : Workshop: Architectural and design risk analysis
Presentations: Architectural risk analyses (English), André N. Klingsheim and Lars-Helge Netland 
Location     : TTY Amsterdam, Kerkstraat 342, 1017 JA Amsterdam
Sponsor      : TTY Internet Solutions

Announcement December 11th 2008: Architectural and design risk analysis

Summary
The main goal of the upcoming OWASP-NL meeting is to provide information to managers, architects, designers, developers and security and risk professionals about risk analyses in the architectural and design phases. The speakers will give specific examples and there will be time to ask questions.
Please register before December 8th because of the necessary catering arrangements.

Location
The location and catering is provided by the sponsor of this meeting:

Program
17.30 – 18.30 Check-In (catering included)

18.30 – 19:00 Introduction (OWASP organization, projects, sponsor)

19.00 – 21.00 Architectural risk analyses (English), André N. Klingsheim and Lars-Helge Netland
This workshop will explore how businesses can use risk analysis in the architecture/design phase of software development to produce more secure software. Participants will get an introduction to risk analysis, which will cover both definitions and how to apply the concepts in practice. The workshop consists of four parts: a short overview of current security threats; an introduction to risk management; an exploration of the limitations of risk management; and some real world applications of the presented techniques.
Lars-Helge Netland and André N. Klingsheim are software security analysts at, and co-owners of, NoWires Group AS. They both hold PhD degrees in applied software security, focused on risk analysis of software architecture and design.

20.00 – 20:15 Break

21.15 – 21:30 Discussion, questions and social

If you want to attend, please send an email to: [email protected].
Please register before December 8th, because of the necessary catering arrangements.

All OWASP chapter meetings are free of charge and you don’t have to be an OWASP member to attend. There are never any vendor pitches or sales presentations at OWASP meetings.

NOTE TO CISSP's: OWASP Meetings count towards CPE Credits.

The announcement and full descriptions can be found here:
Media:Announcement_11_December.pdf

Meeting minutes October 27th 2008

At October 27th, the Dutch OWASP chapter came together at the office of the sponsor of the evening; ps_testware in Doorn. The subject of the evening was 'Privacy and the Internet’. There were 2 speakers and approximately 25 attendees.

After a short welcome talk by both the sponsor and OWASP, Mario de Boer had an announcement about a new OWASP project; ORPRO, the Open Review Project. The goal of the project is to review Open Source Software from an independent point of view. Reviews will be done both manually and with the aid of source code analysis software provided by Fortify. The first software package to be reviewed is already available so reviewers are needed. More information can be found on the OWASP project page. [1]

First presentation: Privacy & the Internet presented by Frank Fruijthoff and Ellen Hoving.
The goal of this presentation was to show the problems in regulating privacy on the internet by law. The presentation was roughly split in 3 parts: definitions, requirements and context.
The main problem with regulating privacy is that the concept of privacy is very broad and not well defined. Privacy can have different meanings and consequences in different contexts. Most laws therefore focus on the individual and define privacy as 'protection of personal information' where 'personal information' is all data that can be tracked back to a single person. The last years many countries within the EU developed internet laws concerning privacy on the internet. These laws state that information can only be used what it originally was intended for and usage of that information must be reported at central register. This register also makes it possible to file a complaint and check what companies use personal information for what purposes. While these rules are mostly sufficient for local databases they often fail when applied to information stored on or with use of the internet. Problems encountered are captured in the "four D's";
- Internet is deterritorialized; internet has no boundaries.
- Internet is deregulated; internet has no law, only terms of use.
- Internet is dematerialized; internet is not physical.
- Internet is decentralized; there is no single regulating or controlling organization.
Although the protection of personal data is more and more covered by laws, the increasing usage of external storage and connections over the internet will make it harder to enforce them. The main conclusion of the evening was that, although many initiatives improving privacy exist, the very properties of the internet make it hard to ensure privacy completely.

Second presentation: Vulnerability and source code scanners presented by E. Strijbos. This presentation showed the results of a research concerning the feasibility of a Web Application Security Certification by the usage of vulnerability scanners.
With the daily increasing amount of threads and vulnerabilities in web applications there is a market-driven demand for an independent and automated scan service. Current scan services often lack coverage and depth of scanning and give no details about the used scanning methods.
In this research several commercial vulnerability scanners and static analysis tools were compared and checked for scantime, accuracy, false positives, and ease of use. The results showed that almost all scanners find most of the vulnerabilities, but also produce many false positives. Also, without proper configuration the amount of results can be overwhelming and inconclusive. Furthermore results showed that static analysis scanners are much faster than vulnerability scanners, but have a more limited usage. The main conclusion was that although vulnerability scanners and static analysis tools can be very helpful in identifying vulnerabilities, their current efficiency is not high enough to use as the basis for an automated vulnerability scan.

Meeting October 27th 2008: Privacy and the Internet

Summary
The main goal of the upcoming OWASP-NL meeting is to provide information to developers and security professionals about personal and technical privacy on the internet. The speakers focus on privacy regulations related to the internet and on the mass amount of personal and technical information available about persons and companies on the internet, with and without their consent. Furthermore tools will be discussed that help prevent leakage of privacy related and other kind of data. They will give specific examples and there will be time to ask questions.
Please register before October 20th because of the necessary catering arrangements.

Location
The location and catering is provided by the sponsor of this meeting:

Program
17.30 - 18.30 Check-In (catering included)

18.30 – 19:00 Introduction (OWASP organization, projects, sponsor)

19.00 - 20.15 Privacy and Internet (Dutch), Frank Fruijthoff and Ellen Hoving
In this presentation the general principles of privacy laws in the Netherlands and the EU and specifically privacy and the internet will be covered.
Frank Fruijthoff is a Compliance Officer with ING. He has a Compliance and Risk Management background and is specialised in privacy.
Ellen Hoving is a graduated lawyer. She works as an independent consultant specialized in compliance and privacy.

20.15 – 20:30 Break

20:30 – 21:00 Vulnerability and source code scanners (Dutch), Emile Strijbos
For his Master thesis in computer science at the Radboud Universiteit in Nijmegen, Emile Strijbos investigated vulnerability scanners and source code scanners. These are automated tools that try to detect security flaws, either in running web-applications or in their source code.
Emile tried out several of these tools, including both free and commercial ones, to see how good they are at detecting standard vulnerabilities, such as SQL injection, XSS, CSRF, etc.

21.00 – 21:30 Discussion, questions and social

If you want to attend, please send an email to: [email protected].
Please register before October 20th, because of the necessary catering arrangements. The number of registries is limited to 50 due to the capacity of the location and will be handled in order of receipt.

All OWASP chapter meetings are free of charge and you don’t have to be an OWASP member to attend. There are never any vendor pitches or sales presentations at OWASP meetings.

NOTE TO CISSP's: OWASP Meetings count towards CPE Credits.

The announcement and full descriptions can be found here:
Media:Announcement_27_Oktober.pdf

Meeting minutes March 23th 2008

At March 23th, the Dutch OWASP chapter came together in the Mercury hotel in Nieuwegein. The meeting was sponsored by Fortify Software. The subject of the evening was 'Software Vulnerability Assesment’. There were 3 speakers and approximately 40 attendees.

After a short introduction of Migchiel de Jong (Fortify) about the subject of Static and Dynamic Analysis and the tools that Fortify provides the speakers of the evening where introduced.

First presentation: Practices of Complex(ity) matters (Dutch), Mario de Boer
Mario de Boer has spent much of his free time the last 16 years into disassembling various pieces of software and analyzing the code and its statistics. The main advantage in analyzing binaries is that no access to source code is needed, all dependencies (i.e. the compiler) are included and it’s independent of the tool used. Disassembling compiled code gives great insight in the complexity of the software and the entry and exit points of data. Although there is no direct relation between the complexity of software and its security, statistically the most vulnerabilities appear in the most complex portions of a program. Data entry points in complex portions of the code can give rise to possible exploits so static analysis can give insight in the most vulnerable places in software which is useful information in testing. The disadvantages of static analysis are that an extensive knowledge of assembly is needed and, due to its statistic nature, it gives rise to many false positives. In conclusion static binary analysis, when used by experts, can be a powerful tool to gain insight in the most vulnerable parts of the software and be a valuable tool in both developing and testing software.

Second presentation: V.A.C: SQL injection (Dutch), Marinus Kuivenhoven
A new reoccurring topic on OWASP presentations will be the so called VAC. In these presentations an expert will talk about a Vulnerability, how to Assess it and possible Countermeasures. This evening Marinus started with the second vulnerability in the OWASP top ten; SQL injections.
With the aid of Webgoat, a few simple examples and the possible consequences were shown. SQL injection is particularly useful exploit in the reconnaissance phase since it can be abused for information leakage and in getting information about e.g. the table structure.
On the internet and in literature many countermeasures against SQL injections are described. However, many of these countermeasures are not usable in a maintainable system or cannot prevent SQL injections completely. The most important conclusion was that input should never be trusted and should never be directly used.

Third presentation: Secure Programming with Static Analysis (English), Brian Chess
The last speaker of the evening was Brian Chess who presented his new book ‘Secure Programming with Static Analysis’. Brian made clear that, although a powerful tool, static binary analysis is already too late in the SDLC to be successful in preventing vulnerabilities. Scanning for possible vulnerabilities should be implemented as early as possible i.e. during coding. The main advantages of static analysis are the cost and speed. Since errors and bad practices are identified in an early stage they can be solved at the spot, making auditing the software more efficient in term of time and depth.
Static analysis can successfully be used for style and type checking, program understanding and verification, and for security reviews. The success of static analysis, however, is fully depending on the rules implemented in the scanner. Static analysis is also unable to identify design flaws, right problems, or wrong user input.
The conclusion was that scanning for vulnerabilities can probably only be successful with the aid of static analysis, but many requirements should be met. Firstly it should become part of the SDLC and culture. Secondly the right tool should be picked and people should be trained in its use. Lastly investments should be made in building up a good rule set and metrics.

Meeting March 26th 2008: Software Vulnerability assessment

Summary
The main goal of the upcoming OWASP-NL meeting is to provide information to developers and security professionals involved in creating secure (web-)applications. The main focus will be on software vulnerability assessment. The speakers will give specific examples and of course there is time to ask questions about your own experiences.

Location
The location and catering is provided by the sponsor of this meeting:

Program
17.30 - 18.30 Check-In (catering included)

18.30 - 18:50 Introduction (OWASP, sponsor)

18.50 - 19.30 Complex(ity) matters (Dutch), Mario de Boer
Various methods exist to locate specific vulnerabilities in software. In the presentation we will look at static analysis of binaries, and the problems we face when trying to locate vulnerabilities. Several ideas will be discussed to make the search easier, but at the same time less exact. The first idea is trivial: automate as much as possible. The second idea is nearly trivial: don't aim at exact vulnerabilities but relax the search to locating potential vulnerabilities. We will give examples that illustrate the results.
Mario de Boer is a senior security consultant at Logica, and as such focuses on security management aspects like security frameworks, compliance, monitoring and control and risk management. Before joining Logica, Mario worked at the Dutch ministries of Defense and Justice, he co-founded a security company and worked as a project manager in the financial sector. For several years he taught courses in software security analysis and secure software development. Besides security management, Mario has interest in software security, reverse engineering and cryptography. Within Logica Netherlands, he is knowledge manager application security. Mario holds a PhD in Mathematics and is CISA and CISSP.

19.30 - 19:50 Break

19:50 - 20:20 V.A.C: SQL injection (Dutch), Marinus Kuivenhoven
Vulnerability:
An application which uses a database for its information needs, communicates with it trough SQL. SQL injection is an attack in which malicious code is inserted into strings that are later passed to an instance of a Database for parsing and execution.
Assessment:
SQL injection can threaten the confidentiality, availability and integrity of the data. The various types of SQL injection and their impact will be shown.
Countermeasure:
Any procedure that constructs SQL statements should be reviewed for injection vulnerabilities because a database will execute all syntactically valid queries that it receives. How this should be done will be shown for the most popular languages.
Marinus is a Technology Specialist with Sogeti Nederland B.V. specializing in service oriented architectures and secure application development. His experience includes developing and administrating Oracle-based systems.

20.20 - 21.00 Secure Programming with Static Analysis (English), Brian Chess
Creating secure code requires more than just good intentions. Programmers need to know how to make their code safe in an almost infinite number of scenarios and configurations. Static source code analysis gives users the ability to review their work with a fine tooth comb and uncover the kinds of errors that lead directly to vulnerabilities. This talk frames the software security problem and shows how static analysis is part of the solution. We will look at how static analysis works, how to integrate it into the software development processes, and how to make the most of it during security code review. Along the way we'll look at examples taken from real-world security incidents, showing how coding errors are exploited, how they could have been prevented, and how static analysis can rapidly uncover similar errors.
Brian Chess is a founder of Fortify Software and serves as Fortify's Chief Scientist, where his work focuses on practical methods for creating secure systems. His book, Secure Programming with Static Analysis, shows how static source code analysis is an indispensable tool for getting security right. Brian holds a Ph.D. in computer engineering from the University of California at Santa Cruz, where he studied the application of static analysis to the problem of finding security-relevant defects in source code. Before settling on security, Brian spent a decade in Silicon Valley working at huge companies and small startups. He has done research on a broad set of topics, ranging from integrated circuit design all the way to delivering software as a service.

21.00 - 21:30 Discussion, questions and social

Registration
If you want to attend, please send an email to: [email protected].

All OWASP chapter meetings are free of charge and you don’t have to be an OWASP member to attend. There are never any vendor pitches or sales presentations at OWASP meetings.

NOTE TO CISSP's: OWASP Meetings count towards CPE Credits.

Meeting minutes December 20th 2007

At December 20th, the Dutch OWASP chapter came together at the office of ps_testware located in Doorn. The subject of the evening was 'creating secure (web)applications. There were 3 speakers and close to 30 attendees

First presentation: Practices of developing optimal security (dutch), Andre Post
Andre talked from his rich experience as software auditor and code reviewer. Based on his experience he stated that developing good, secure software can only be done with developers with the right set of mind. Security should not be tested into the software, but should be a natural thing for developers to develop into the software. For this you need developers who know by heart when security flaws start to exist and how to prevent them. Developers with the necessary experience are rare and often developer teams do not have the right expertise for developing secure software. The most important conclusion of his speech was that secure software starts with security aware developers.

Second presentation: Problems of developing secure and correct applications (dutch), Erik Poll
Erik Poll stated that besides having developers who are aware of security, you should also have developers that now the limitations and inherent security leaks of the used language. One of the problems is that many developers are not taught the inherent security holes in programming languages during their education.
Another problem is that software is often made secure for the wrong reasons. At this moment only two reasons appear to be the drive behind developing secure software: economics and laws. Security is mostly of secondary concern and as such will only be implemented at minimum requirements. Bad examples of big companies who develop insecure software and still be successful even further restrict the demand for secure software.
On the positive side many developers make the same mistakes so testing for common security holes can easily be done with checklists and validation tools. These validation tools can be made more successful with the use of metatags in the code.
Erik concluded his speech that improving the secureness of software can only be achieved when there is commitment, the knowledge is available and software is developed and implemented with a secure mind.

Third presentation: Protecting Web services and Web applications against security threats, Rix Groenboom
The third presentation was about a problem which probably will become bigger and bigger the coming years. Although security might be in the scope when developing software at this moment, it certainly was not a requirement 20 or more years ago. Despite their intrinsic insecureness, these systems are connected more and more to the world wide web to meet de demands for online availability. This imposes a major security risk which will become more evident in the years to come and might become bigger than the Y2K problem. Unlike modern software, these applications can only be made secure enough by using advanced testing strategies combined with the use of test-tools and thorough regression tests. Testing alone however is not enough; to accomplish maximum secureness all connections to these systems should be based on a 'deny unless' instead of an 'allow unless' basis.
The conclusion of Rix's talk was that old systems connected to new interfaces should be treated as insecure and all possible precautions should be taken to achieve an acceptable level of secureness.

Meeting December 20th 2007: Secure Development

Summary
The main goal of the upcoming OWASP-NL meeting is to provide information to developers and security professionals involved in creating secure (web-)applications. The general and specific security issues involved on project and programming level will be covered from a practical as well as a theoretical point of view. The speakers will give specific examples and of course there is time to ask questions about your own experiences.
Please register before December the 14th because of the necessary catering arrangements.

Location
The location and catering is provided by the sponsor of this meeting:

Program
17.30 - 18.30 Check-In (catering included)

18.30 – 19:00 Introduction (OWASP organization, projects, sponsor)

19.00 - 19.30 Practices of developing optimal security (dutch), Andre Post
This presentation highlights a number of current practices that lead to sub-optimal security, and suggests ways of avoiding these problems, focusing on the technical side of development.
André Post works for Fox-IT on a variety of projects including core product development, software architecting, security code reviews, and software project management.

19.30 – 19:45 Break

19:45 – 20:30 Problems of developing secure and correct applications (dutch), Erik Poll (slides of the presentation)
This presentation will discuss different possibilities to improve software security. The problem of getting time and money available to be spend on security, not only for developing applications, but also for developing programming languages, will be raised.
Erik Poll is head of the Security of Systems (SoS) group at the Radboud University of Nijmegen. His research does focus on the security and correctness of software.

20.30 - 21.00 Protecting Web services and Web applications against security threats (dutch), Rix Groenboom
During this session, Rix will explore how to implement development and security best practices in the code to make sure that your webservices and applications perform solidly when they are being hacked or used in malicious ways.
Rix Groenboom supports fortune 2000 companies in field automated software error prevention and correction for Parasoft. His main area of expertise is in the use of formal languages for the specification, design and validation of software applications.

21.00 – 21:30 Discussion, questions and social

All OWASP chapter meetings are free of charge and you don’t have to be an OWASP member to attend. There are never any vendor pitches or sales presentations at OWASP meetings.

NOTE TO CISSP's: OWASP Meetings count towards CPE Credits.

The announcement and full descriptions can be found here:
Media:Announcement_20_December.pdf
Media:Announcement_20_December_2.pdf

Meeting September 13th: putting initiatives into practice

The main goal of the next OWASP meeting is finding a way to put initiatives and all offered help into a form of structural benefit for the OWASP Netherlands local chapter. As a starting point for the discussion, examples will be taken from other European chapters and input delivered by discussions that take place on the mailing list is considered too. Let this be a call to put your ideas on the mailing list before the next meeting!

The location is provided by the sponsor of this meeting:
Comsec Consulting BV
Rivium Boulevard 102
2909LK Capelle aan den IJssel

The agenda:
18.00 - 18.30 Check-In (catering included)
18.30 - 18.45 OWASP update, Bert Koelewijn
18.45 - 19.15 Security Best Practices for .NET, Boaz Shunami
19.15 - 20.00 Discussion: collecting ideas and initiatives
20.00 - 20.15 Coffee break
20.15 - 21.00 Discussion: how to enable community commitment
21.00 - 21.30 Closing discussion and coffee

Boaz Shunami
Boaz is manager of the Application Security department of Comsec Europe. He has 11 years of experience in the IT Security field, and a large part of them in Application Security.
Boaz did numerous application security audits in very large organizations and is recognized as one of the greatest expert’s world wide. Boaz' expertise is broad, but especially in-depth for the .NET platform.

Discussion input (until now)
- division of local chapter work load by multiple people
- collaboration with other organizations

If you want to attend send an email to [email protected].

All OWASP chapter meetings are free, there are never vendor pitches or sales presentations at OWASP meetings.

NOTE TO CISSP's: OWASP Meetings count towards CPE Credits.

Meeting minutes Januar 11th 2007

January 11th, the Dutch OWASP chapter came together at the office of Sogeti Netherlands. Subject of the evening was 'putting software security into practice'. The group was small but select.

The agenda:
18.00 - 18.30 Check-In (catering included)
18.30 - 18.45 Sponsor opening
18.45 - 19.00 OWASP update, Bert Koelewijn
19.00 - 19.30 Implementation of Security by Design, Martin Knobloch
19.30 - 19.45 Panel introduction
19.45 - 20.00 Coffee break
20.00 - 21.30 Panel discussion

After being welcomed by Frank Langeveld from Sogeti and Bert Koelewijn, Dutch chapter leader, the evening started with the presentation 'Security By Design'. During the presentation Martin Knobloch told about his experiences during the implementation of the Secure Development Life Cycle in a company like Sogeti Nederland B.V.

The presentation is available here:
Media:Implementation_of_Security_by_Design.ppt

After a small break, the panel discussion started with the following panel: Henk van der Heijden - Comsec Consulting, Dr.ir. Mario de Boer - LogicaCMG and Martin Knobloch - Sogeti Nederland.
During the discussion, it became clear people are struggling to get the Secure Development Life Cycle implemented in their company. The various experiences were shared with the panel and the others. Company typical problems and common misunderstandings about Software security where brought up.
The consensus of the discussion was that the main problem lies in the lack of security awareness and knowledge of the managers and the developers. And this of course is exactly where OWASP comes in…

Meeting Januar 11th 2007

The OWASP meeting of 11 January is about putting software security into practice. A lot of books, standards, organizations and consultants tell us how we should develop secure software. But which methods and measures are commonly adopted and which are not and why?
This will be the main focus of the discussion that we will have with a panel of people that experienced implementing software security in the field.

The location is provided by the sponsor of this meeting:
Sogeti Nederland B.V.
"La Charmille" building
Lange Dreef 17
4131 NJ Vianen

The agenda:
18.00 - 18.30 Check-In (catering included)
18.30 - 18.45 Sponsor opening
18.45 - 19.00 OWASP update, Bert Koelewijn
19.00 - 19.30 Implementation of Security by Design, Martin Knobloch
19.30 - 19.45 Panel introduction
19.45 - 20.00 Coffee break
20.00 - 21.30 Panel discussion

Implementation of Security by Design
What is needed to implement a 'Secure Development Life Cycle' within Sogeti Nederland? The speaker started a project called 'Security by Design' in march 2006 implementing a SDLC at Sogeti Nederland.
In his presentation, the speaker will share his technical and organizational experiences that he gained with the still ongoing implementation.

About the speaker
Martin Knobloch has more than 8 years experience in design and development of J2EE applications for customers in various sectors of the market. In September 2003 Martin Knobloch started working for Sogeti Nederland, where he does the design, development and review of J2EE applications and architectures.
From this background, Martin Knobloch experienced the threats of insecure software firsthand. In march 2006, Martin Knobloch started implementing a SDLC within Sogeti Nederland.

Panel discussion
The panel members are:
Henk van der Heijden, Managing Director - Comsec Consulting B.V.
Dr.ir. Mario de Boer, Security Consultant - LogicaCMG
Martin Knobloch, Senior Technologie Specialist - Sogeti Nederland B.V.

In the discussion, we will try to find answers to questions like:
- What are the most common security practices in software development?
- How effective are those practices?
- Where do we start practicing security?
- What should be the most common security practices in software development?
- How much does security cost?
- How does the Systems Security Engineering Capability Maturity Model (SSE-CMM) fit in?

If you want to attend send an email to [email protected].

All OWASP chapter meetings are free, there are never vendor pitches or sales presentations at OWASP meetings.

NOTE TO CISSP’s: OWASP Meetings count towards CPE Credits.

Meeting minutes March 9thh 2007

On 9 march, the second meeting of OWASP Netherlands local chapter took place. GetronicsPinkRoccade provided the venue, in their luxury conference centre: Connection I.

Agenda:
18.00 - 18.45 Check-In (bread & drinks)
18.45 - 19.00 Opening
19.00 - 20.00 Improving Security in the Application Development Life-cycle, Migchiel de Jong
20.00 - 20.15 Coffee break
20.15 - 22.00 Form focus groups

The presentation of Migchiel de Jong was found very interesting by the audience. At the end of his presentation, he demonstrated a static code analysis of the OWASP webgoat application.

After the coffee break, the attendances started discussing about the largest common topics of interest in the web application security field, in relation to the OWASP Netherlands chapter. As a result, the following focus groups are formed:

Testing
The current OWASP Testing project and the Open Source Security Testing Methodology Manual of ISECOM, provide guidelines and best practices for testers. These guidelines can be used to formalize a standard structure and a set of minimum requirements for a security test. Clients could ask a tester to adhere to these guidelines.
A second idea is to standardize the testing results management report. In practice, testing could result in piles of paper with all the findings. The real value is reporting it in a usable way. For example: mapping technical findings to business risks.

Frans v. Buul
Peter Gouwentak
Arthur Donkers
Eelco Klaver
Migchiel de Jong
Mario de Boer

First focus group meeting: Monday 27 march, 18:00h, PwC Utrecht


Public Relations
This focus group will try to make business aware of the security impact that developing, hosting and using web applications has. What OWASP is and how OWASP can help. This can be done by giving presentations, writing papers and articles, word of mouth, etc. etc.

Remco Bakker
Ronald Eygendaal
Bas van Vossen
Edwin van Vliet
Eelco Klaver

First presentation of OWASP materials: Edwin van Vliet, TestNet - Voorjaarsevenement, 5 april
First focus group meeting: To be planned!


Education
OWASP and universities/schools could benefit from working together. For example:
- OWASP provides lot's of materials usable in colleges.
- Develop OWASP training course.
- Students can participate in OWASP projects
- OWASP can provide a platform for supporting research. Such as thesis projects, etc.
- OWASP representatives could provide guest colleges.

Ronald Eygendaal
Erik Poll
Bas van Vossen
Edwin van Vliet

First focus group meeting: To be planned!

The presentation is available here:
Media:OWASP_NL_Fortify_Software.pdf

Meeting March 9th 2007: Second meeting of the OWASP Netherlands local chapter!

In this second meeting focus groups are to be formed, to discuss common problems, develop and research common solutions in a vendor neutral environment. So this is a very good opportunity to get in contact with others, to exchange knowledge and experiences on specific topics.

For every focus group the following questions has to be answered:
1. Which specific topic is to be addressed?
2. What are the deliverables?
3. What is the relation to OWASP? (Current projects, materials, expertise and knowledge interchange, etc.)
4. Who is the central contact of the subgroup?

It would be nice to have a bigger and more diverse group, compared to the first meeting. So let's recall: "Please, bring at least one friend, next time." And don't hesitate to send this announcement to everybody who may be interested!

We thank Getronics PinkRoccade for offering us a venue:
Getronics PinkRoccade
Fauststraat 1
7323 BA Apeldoorn

The agenda:
18.00 - 18.30 Check-In
18.30 - 18.45 Opening
18.45 - 19.30 Improving Security in the Application Development Life-cycle, Migchiel de Jong
19.30 - 20.00 Collecting focus group initiatives
19.45 - 20.00 Coffee break
20.00 - 21.00 Form focus groups

Presentation Abstract
Rather than spending large amounts of time and money on proving that we have security vulnerabilities after programs go into production, companies should go to the source and correct vulnerabilities as early as possible in the development stage. It is unquestionably faster, simpler, and cheaper for developers to correct vulnerabilities as they build programs.
But how can development management ensure that developers focus on security when there is no time or budget for security at the development stage? Even with the correct focus, how can they learn what to look for? How can they stay ahead of the dedicated and resourceful hacker?
The answer is effective processes and better tools. With advanced software security tools, a developer can pinpoint vulnerabilities in a matter of seconds — the same vulnerabilities that would take a hacker or manual code reviewer weeks or even months to find. These same tools can give development and information security managers useful metrics on application vulnerabilities before they are released into deployment.
This talk will walk through the Application Development Life-Cycle and discuss how tools can help come to grips with software security issues in a particular phase.

About the presenter
Migchiel de Jong has developed hardware and software for 10 years before joining Rational Software. During the 5 years at Rational Software (later acquired by IBM) he was involved in many software development process improvement projects. Currently Migchiel de Jong is working at Fortify Software, Palo Alto, California, as a software security engineer.

If you want to attend send an email to [email protected]. Please don't wait, 9 march is not that long anymore!

All OWASP chapter meetings are free, there are never vendor pitches or sales presentations at OWASP meetings.

NOTE TO CISSP’s: OWASP Meetings count towards CPE Credits.

OWASP Netherlands kick-off meeting minutes

On 17 November, OWASP Netherlands had it's first meeting. We moved to a bigger location, the Mercure hotel in Nieuwegein, to host all the 35 attendees.

The agenda:
18.00 - 18.30 Check-In (bread & drinks)
18.30 - 18.45 Chapter opening
18.45 - 19.30 Presentation - 'Top tien web applicatie kwetsbaarheden in J2EE', Eelco Klaver
19.30 - 19.45 Presentation - 'Veilige webapplicaties boven alles', Mike Wardi
19.45 - 20.00 Coffee break
20.00 - 21.00 Discussion - About the OWASP Netherlands local chapter

The discussion took place in a 'round table' session, where all attendees were able to take part. The focus of the discussion was how to give the OWASP Netherlands local chapter additional value, next to the OWASP project. What the goals and tasks will be. And which actions will have to be taken at short term.
Different people have interest in different subjects. In general meetings there is no time to address all subjects and address them specific enough. Therefore subgroups can be formed, focusing on specific topics. They can have their own communication channel and meetings, but should keep close contact with the OWASP body.

An inventarisation:

Discussion Topics
- Awareness: writing articles, press publications, interviews
- Education: contact universities, schools and their common boards. Develop and gather education materials.
- General: discuss ideas for OWASP NL

Focusgroup Topics
- (dutch) metrics project
- (dutch) legal project
- standard framework for pentest reports
- safe outsourcing

Actions that should be taken on short term are:
- provide communication channels
- plan next (sub)meetings
- start discussions and focusgroups

The presentations are available here:

Media:OWASP_NL_Top_Ten_Web_Application_Vulnerabilities_in_J2EE.pdf
Media:OWASP_NL_Veilige_Web_App_Boven_Alles.pdf

You are welcome to the OWASP Netherlands local chapter kick-off meeting!

Thursday, November 17th (2005) at 18.00h.

ATTENTION! Because of the large amount of attendees, the location has changed:

Hotel Mercure Utrecht/Nieuwegein
Buizerdlaan 10
3435 SB NIEUWEGEIN
Tel: 00 31 (0) 30 60 84 122
Fax: 00 31 (0) 30 60 38 374

This first meeting will be an introduction to the OWASP. A constructive discussion will be held about the actual form of the OWASP Netherlands local chapter.

The agenda:
18.00 - 18.30 Check-In (bread & drinks)
18.30 - 18.45 Chapter opening
18.45 - 19.30 Presentation - 'Top tien web applicatie kwetsbaarheden in J2EE', Eelco Klaver
19.30 - 19.45 Presentation - 'Veilige webapplicaties boven alles', Mike Wardi
19.45 - 20.00 Coffee break
20.00 - 21.00 Discussion - About the OWASP Netherlands local chapter

About the presenters

Eelco Klaver
Eelco Klaver is a senior consultant for Xebia IT Architects, since 2003. Doing software reviews, security audits and giving security workshops are part of his job. He has almost 10 years experience with developing enterprise applications in J2EE for different employees. At the moment, Eelco is the front man of the security business unit for Xebia, focussing on the security aspects of enterprise applications build on J2EE.

Mike Wardi
Mike Wardi is an internet application manager for a financial institute. He's responsible for the safety of internet applications provided to customers and the implementation of the security policies in software developement.


If you want to attend, please send an email to [email protected] or the mailing list.

All OWASP chapter meetings are free! There are never vendor pitches or sales presentations at OWASP meetings.

NOTE TO CISSP’s: OWASP Meetings count towards CPE Credits.