<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/index.php?action=history&amp;feed=atom&amp;title=6th_OWASP_IL_chapter_meeting</id>
		<title>6th OWASP IL chapter meeting - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/index.php?action=history&amp;feed=atom&amp;title=6th_OWASP_IL_chapter_meeting"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=6th_OWASP_IL_chapter_meeting&amp;action=history"/>
		<updated>2026-04-11T11:05:48Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=6th_OWASP_IL_chapter_meeting&amp;diff=20971&amp;oldid=prev</id>
		<title>Oshezaf: New page: == At Breach Security, January 24th 2007 ==  The 6th OWASP IL meeting was held on January 24th 2007, at 17:15, at Breach Security offices in Herzelya and was sponsored by [[www.breach.com|...</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=6th_OWASP_IL_chapter_meeting&amp;diff=20971&amp;oldid=prev"/>
				<updated>2007-08-20T16:21:44Z</updated>
		
		<summary type="html">&lt;p&gt;New page: == At Breach Security, January 24th 2007 ==  The 6th OWASP IL meeting was held on January 24th 2007, at 17:15, at Breach Security offices in Herzelya and was sponsored by [[www.breach.com|...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== At Breach Security, January 24th 2007 ==&lt;br /&gt;
&lt;br /&gt;
The 6th OWASP IL meeting was held on January 24th 2007, at 17:15, at Breach Security offices in Herzelya and was sponsored by [[www.breach.com|Breach Security]]. The meeting was very successful, with nearly 50 people attending the meeting.&lt;br /&gt;
&lt;br /&gt;
The agenda of the meeting was:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;big&amp;gt;'''[[media:OWASP_IL_Source_Code_Analysis_and_Application_Security.pdf|Source Code Analysis and Application Security - Cheating the Maze]]'''&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Maty Siman, Founder &amp;amp; CTO, [http://www.checkmarx.com/ Checkmarx]'''&lt;br /&gt;
&lt;br /&gt;
During the last few years automatically analyzing source code in order to find security vulnerabilities became a popular method in the field of Application Security. The presentation will discuss the theory and research of static code analysis, the application of static code analysis for security, comparing this method to other application security defense technologies and will demonstrate the use of static code analysis for application security.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;big&amp;gt;'''[[media:OWASP_IL_WCF_Security.pdf|Security Implications of .Net 3.0 and the Windows Communication Foundation (WCF)]]'''&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Emmanuel Cohen-Yashar (Manu), Senior .NET technology consultant, [http://www.sela.co.il Sela Group]'''   &lt;br /&gt;
&lt;br /&gt;
Windows Communication Foundation (WCF) is the new Microsoft communication framework bundled as part of of .NET Framework 3.0, the new .NET Windows API succeeding Win32 with the release of Windows Vista. WCF programming model unifies Web Services, .NET Remoting, Distributed Transactions, and Message Queues into a single Service-oriented programming model for distributed computing. The presentation will describe the tenets of SOA – Service Oriented Architecture, introduce WCF and discuss the security implications of this broad new communication paradigm.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;big&amp;gt;'''[[media:OWASP_IL_The_Universal_XSS_PDF_Vulnerability.pdf|Analysis of the Universal XSS PDF vulnerability - Cause, Solutions and Fun Stuff]]'''&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Ofer Shezaf, CTO, [http://www.breach.com Breach Security], Leader of [http://www.modsecurity.org/projects/rules/index.html ModSecurity Core Rule Set] open source project '''&lt;br /&gt;
&lt;br /&gt;
Recently a new vulnerability was discovered in commonly used versions of Adobe Acrobat software. Unlike common XSS attacks that require a specific vulnerability in the attacked web site, in this case the vulnerability in Acrobat is sufficient and no fault is required in the attacked web site, and any site that serves PDF files is vulnerable. Therefore it is called &amp;quot;universal XSS&amp;quot; vulnerability.&lt;br /&gt;
&lt;br /&gt;
The presentation will describe the vulnerability, the theoretical and practical solutions for the vulnerability as well as some very funny stories about the dynamics of such a high profile vulnerability, or in other words, what happens when you try to get a car mechanic to fix an application security vulnerability.&lt;/div&gt;</summary>
		<author><name>Oshezaf</name></author>	</entry>

	</feed>