<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mohammed+ALDOUB</id>
		<title>OWASP - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mohammed+ALDOUB"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/Mohammed_ALDOUB"/>
		<updated>2026-04-23T03:39:45Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=234045</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=234045"/>
				<updated>2017-10-03T17:16:24Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: Addition of 2016 activities and 2017 events&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Inactive Chapter}}&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:Owasp_kuwait.png]]&lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The chapter leader position is OPEN,&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
3- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Evil Shell: Hacking Linux Users, in Riyadh , May 2016, which can be viewed [https://www.slideshare.net/Voulnet/evil-shell-hacking-linux-users here].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News == &lt;br /&gt;
&lt;br /&gt;
Next Lecture and OWASP Kuwait Chapter Meeting on 4th of October, 2017, in Kuwait University, Khaldiya Campus, Hall 109, from 12:30PM to 2PM. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Linux Security Lecture in Riyadh, May 2016 by Mohammed ALDOUB, Kuwait chapter leader.  &lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Media:InvadersAtTheGates.ppt]]&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
 '''Second Meeting Location مكان اللقاء الثاني'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
4 من اكتوبر 2017، الساعة 12:30 مساءً&lt;br /&gt;
October the 4th, 2017. At 12:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن تطبيقات الويب وحمايتها وثغراتها و كيفية الدفاع عنها .&lt;br /&gt;
&lt;br /&gt;
Introduction to web app security, attacks, and defenses.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
جامعة الكويت، كلية الهندسة، قاعة 109&lt;br /&gt;
Kuwait University, Khaldiya Campus, Hall 109&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Statement_on_the_Security_of_the_Internet_2014/ar&amp;diff=167100</id>
		<title>OWASP Statement on the Security of the Internet 2014/ar</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Statement_on_the_Security_of_the_Internet_2014/ar&amp;diff=167100"/>
				<updated>2014-01-31T07:08:02Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;text-align: right; direction: rtl; margin-left: 1em;&amp;quot;&amp;gt;&lt;br /&gt;
مجتمع أواسب يهتم كثيرا بثقة الناس بخدمات الانترنت و التطبيقات التي تتصل بها، لذلك فإن التقارير الحديثة التي ذكرت عمليات التجسس واسعة النطاق على اتصالات الانترنت وبرامجه، ومحاولات اضعاف معايير التشفير، كلها تسبب لنا قلق واهتمام كبيرين. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
كنا نعلم عن عمليات التنصت والتعقب ضد الأفراد المستهدفين، ولكن حجم عمليات التجسس واسعة النطاق التي انكشفت مؤخرا كانت بمثابة إنذار شديد اللهجة. &lt;br /&gt;
بكل تأكيد فإنه من الصعب الجزم بمعرفة أي هجمات يتم حاليا استخدامها، وأي الاتفاقيات السرية قد تكون فعالة، ولذلك فإنه من الصعب على منظمة أواسب التعليق على التفاصيل من منظورها الخاص. &lt;br /&gt;
لدى أواسب مبادئ قديمة حول قيامنا بتوضيح القرارات التي نتخذها. مهمتنا هي الشفافية والوضوح بأمن التطبيقات حتى يتسنى للأفراد والمؤسسات اتخاذ قرارات مبنية على دراية ومعرفة تجاه مخاطر التطبيقات. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نحن نؤمن بشكل أساسي أن التطبيقات والبرامج الآمنة والجديرة بالثقة تشكل حجر أساس لتواصل الناس حول العالم، فلا يتصل الناس ببعضهم غالبا إلا بإستخدامها. &lt;br /&gt;
&lt;br /&gt;
نؤمن أيضا أن المجتمعات والشركات والحكومات يجب عليها أن تحمي أمن البرمجيات وأن لا تتعمد إضعاف أمن البرمجيات أو معايير الأمن أو خوارزميات التشفير. &lt;br /&gt;
&lt;br /&gt;
نؤمن وبشدة أن المجتمعات والشركات والحكومات يجب عليها ألا تتعمد إدخال الثغرات والأخطاء والأبواب الخلفية التي تضعف الأمن والثقة بالبرمجيات والتطبيقات. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
كما أننا نعتقد أنه من المهم التنويه على حقيقة أن هذه الثغرات التي يتم ادخالها خلسة بالبرمجيات لأجل التجسس والمراقبة سيرجع ضررها البالغ على الناس والمجتمع لأنه عاجلا أم آجلا سيتم اكتشافها واستغلالها من قبل المخربين والمجرمين. وأضف إلى هذا حقيقة أن الشركات والمجتمعات ستصبح بلا حماية من هذه الثغرات المتعمدة، وبذلك يتم اضعاف أساس البرمجيات بالكامل والذي يؤثر بشكل مباشر على حياتنا اليومية وعلى نطاق عالمي. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
مجتمع أواسب يريد أن يساهم ببناء أنظمة وبرامج آمنة وقابلة للتطبيق الواقعي لكل مستخدمي الانترنت. معالجة مخاطر وثغرات أمن البرمجيات كان ولا يزال من أهم محاور مجتمع أواسب ومصادر قوته، وهذا المحور لا يقتصر على الجانب التقني فقط، بل يندرج معه محاور مهمة جدا مثل التعليم والقوانين والتطبيق الواقعي وجوانب أخرى. &lt;br /&gt;
بالنسبة لنا فإن الأخبار الأخيرة تمثل تحدي لنا ومصدر إلهام لنتمسك بمبادئنا والعمل الجاد لتأمين الانترنت وبرامجه ومواقعه. &lt;br /&gt;
إيون كيري،وهو أحد أعضاء مجلس إدارة أواسب المنتخبين، يؤكد بحديثه: &amp;quot;أواسب لا يسعها أن تقف مكتوفة الأيدي أمام إضعاف وتآكل الأمن، فهذا ضد مبادئنا&amp;quot;. &lt;br /&gt;
نحن واثقون من قدرة مجتمع أواسب على القيام بدوره ونؤمن بأن أدوات أواسب وبرامجها وتعاليمها، إن تم استخدامها بشكل أوسع، فإنها قادرة على المساهمة. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
يجب علينا استغلال هذه الفرصة لنرى ما الذي يمكننا فعله بشكل أفضل بالمستقبل وليس فقط تحت ضوء الأحداث الراهنة. الأمن والخصوصية بالإنترنت لا يزالون يشكلان تحدي كبير حتى بغض النظر عن النشاطات الاستخباراتية الأخيرة.&lt;br /&gt;
&lt;br /&gt;
يمكن استنباط العديد من الدروس المفيدة للسنين القادمة، و توبياس غوندروم، عضو مجلس إدارة أواسب المنتخب، يؤكد هذا الأمل بقوله: &amp;quot;ربما كانت حوارات هذه السنة هي الشرارة التي تحفز العالم ليصبح أكثر وعيا، و ينتقل من &amp;quot;غير آمن تلقائيا&amp;quot; إلى &amp;quot;آمن تلقائيا&amp;quot;. &amp;quot;&lt;br /&gt;
&lt;br /&gt;
الانتشار العلني والشهرة والتحفيز أمور مهمة أيضا، وهناك الكثير من الأعمال التي يمكن لأي منا القيام بها، ابتداءً من تفعيل المستخدمين للخواص الأمنية إلى قيام المختصين والشركات والحكومات بالتحقق من أن برامجهم ومنتجاتهم وخدماتهم آمنة. &lt;br /&gt;
&lt;br /&gt;
أواسب منظمة ومجتمع مفتوحين ونحن ندعو كل من لديه أي اهتمامات بهذا المجال ليرقى للتحدي ويشارك بتحليل المشكلة والمخاطر ويطور أفكاراً تنفع مستقبلنا المشترك.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Statement_on_the_Security_of_the_Internet_2014/ar&amp;diff=167099</id>
		<title>OWASP Statement on the Security of the Internet 2014/ar</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Statement_on_the_Security_of_the_Internet_2014/ar&amp;diff=167099"/>
				<updated>2014-01-31T07:06:15Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;text-align: right; direction: ltr; margin-left: 1em;&amp;quot;&amp;gt;&lt;br /&gt;
مجتمع أواسب يهتم كثيرا بثقة الناس بخدمات الانترنت و التطبيقات التي تتصل بها، لذلك فإن التقارير الحديثة التي ذكرت عمليات التجسس واسعة النطاق على اتصالات الانترنت وبرامجه، ومحاولات اضعاف معايير التشفير، كلها تسبب لنا قلق واهتمام كبيرين. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
كنا نعلم عن عمليات التنصت والتعقب ضد الأفراد المستهدفين، ولكن حجم عمليات التجسس واسعة النطاق التي انكشفت مؤخرا كانت بمثابة إنذار شديد اللهجة. &lt;br /&gt;
بكل تأكيد فإنه من الصعب الجزم بمعرفة أي هجمات يتم حاليا استخدامها، وأي الاتفاقيات السرية قد تكون فعالة، ولذلك فإنه من الصعب على منظمة أواسب التعليق على التفاصيل من منظورها الخاص. &lt;br /&gt;
لدى أواسب مبادئ قديمة حول قيامنا بتوضيح القرارات التي نتخذها. مهمتنا هي الشفافية والوضوح بأمن التطبيقات حتى يتسنى للأفراد والمؤسسات اتخاذ قرارات مبنية على دراية ومعرفة تجاه مخاطر التطبيقات. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نحن نؤمن بشكل أساسي أن التطبيقات والبرامج الآمنة والجديرة بالثقة تشكل حجر أساس لتواصل الناس حول العالم، فلا يتصل الناس ببعضهم غالبا إلا بإستخدامها. &lt;br /&gt;
&lt;br /&gt;
نؤمن أيضا أن المجتمعات والشركات والحكومات يجب عليها أن تحمي أمن البرمجيات وأن لا تتعمد إضعاف أمن البرمجيات أو معايير الأمن أو خوارزميات التشفير. &lt;br /&gt;
&lt;br /&gt;
نؤمن وبشدة أن المجتمعات والشركات والحكومات يجب عليها ألا تتعمد إدخال الثغرات والأخطاء والأبواب الخلفية التي تضعف الأمن والثقة بالبرمجيات والتطبيقات. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
كما أننا نعتقد أنه من المهم التنويه على حقيقة أن هذه الثغرات التي يتم ادخالها خلسة بالبرمجيات لأجل التجسس والمراقبة سيرجع ضررها البالغ على الناس والمجتمع لأنه عاجلا أم آجلا سيتم اكتشافها واستغلالها من قبل المخربين والمجرمين. وأضف إلى هذا حقيقة أن الشركات والمجتمعات ستصبح بلا حماية من هذه الثغرات المتعمدة، وبذلك يتم اضعاف أساس البرمجيات بالكامل والذي يؤثر بشكل مباشر على حياتنا اليومية وعلى نطاق عالمي. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
مجتمع أواسب يريد أن يساهم ببناء أنظمة وبرامج آمنة وقابلة للتطبيق الواقعي لكل مستخدمي الانترنت. معالجة مخاطر وثغرات أمن البرمجيات كان ولا يزال من أهم محاور مجتمع أواسب ومصادر قوته، وهذا المحور لا يقتصر على الجانب التقني فقط، بل يندرج معه محاور مهمة جدا مثل التعليم والقوانين والتطبيق الواقعي وجوانب أخرى. &lt;br /&gt;
بالنسبة لنا فإن الأخبار الأخيرة تمثل تحدي لنا ومصدر إلهام لنتمسك بمبادئنا والعمل الجاد لتأمين الانترنت وبرامجه ومواقعه. &lt;br /&gt;
إيون كيري،وهو أحد أعضاء مجلس إدارة أواسب المنتخبين، يؤكد بحديثه: &amp;quot;أواسب لا يسعها أن تقف مكتوفة الأيدي أمام إضعاف وتآكل الأمن، فهذا ضد مبادئنا&amp;quot;. &lt;br /&gt;
نحن واثقون من قدرة مجتمع أواسب على القيام بدوره ونؤمن بأن أدوات أواسب وبرامجها وتعاليمها، إن تم استخدامها بشكل أوسع، فإنها قادرة على المساهمة. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
يجب علينا استغلال هذه الفرصة لنرى ما الذي يمكننا فعله بشكل أفضل بالمستقبل وليس فقط تحت ضوء الأحداث الراهنة. الأمن والخصوصية بالإنترنت لا يزالون يشكلان تحدي كبير حتى بغض النظر عن النشاطات الاستخباراتية الأخيرة.&lt;br /&gt;
&lt;br /&gt;
يمكن استنباط العديد من الدروس المفيدة للسنين القادمة، و توبياس غوندروم، عضو مجلس إدارة أواسب المنتخب، يؤكد هذا الأمل بقوله: &amp;quot;ربما كانت حوارات هذه السنة هي الشرارة التي تحفز العالم ليصبح أكثر وعيا، و ينتقل من &amp;quot;غير آمن تلقائيا&amp;quot; إلى &amp;quot;آمن تلقائيا&amp;quot;. &amp;quot;&lt;br /&gt;
&lt;br /&gt;
الانتشار العلني والشهرة والتحفيز أمور مهمة أيضا، وهناك الكثير من الأعمال التي يمكن لأي منا القيام بها، ابتداءً من تفعيل المستخدمين للخواص الأمنية إلى قيام المختصين والشركات والحكومات بالتحقق من أن برامجهم ومنتجاتهم وخدماتهم آمنة. &lt;br /&gt;
&lt;br /&gt;
أواسب منظمة ومجتمع مفتوحين ونحن ندعو كل من لديه أي اهتمامات بهذا المجال ليرقى للتحدي ويشارك بتحليل المشكلة والمخاطر ويطور أفكاراً تنفع مستقبلنا المشترك.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=159795</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=159795"/>
				<updated>2013-10-05T16:44:49Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Owasp_kuwait.png]]&lt;br /&gt;
&lt;br /&gt;
{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Media:InvadersAtTheGates.ppt]]&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:Owasp_kuwait.png&amp;diff=159794</id>
		<title>File:Owasp kuwait.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:Owasp_kuwait.png&amp;diff=159794"/>
				<updated>2013-10-05T16:43:08Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149613</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149613"/>
				<updated>2013-04-11T21:04:21Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Media:InvadersAtTheGates.ppt]]&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149612</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149612"/>
				<updated>2013-04-11T21:03:50Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Media:InvadersAtTheGates.ppt]]&lt;br /&gt;
[[File:InvadersAtTheGates.ppt]]&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149611</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149611"/>
				<updated>2013-04-11T21:02:57Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Media:InvadersAtTheGates.ppt]]&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149610</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149610"/>
				<updated>2013-04-11T21:02:35Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Media:Example.ogg]]&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149609</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149609"/>
				<updated>2013-04-11T21:02:12Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Example.jpg]]&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149608</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149608"/>
				<updated>2013-04-11T20:59:36Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149607</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149607"/>
				<updated>2013-04-11T20:52:45Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt]]&lt;br /&gt;
&lt;br /&gt;
[[Media:https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149606</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149606"/>
				<updated>2013-04-11T20:51:13Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149605</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149605"/>
				<updated>2013-04-11T20:50:54Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt هنا]&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149604</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149604"/>
				<updated>2013-04-11T20:50:02Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة هنا:&lt;br /&gt;
[[File:https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt]]&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download at:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149603</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149603"/>
				<updated>2013-04-11T20:49:36Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded [https://www.owasp.org/images/a/a9/InvadersAtTheGates.ppt here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة هنا:&lt;br /&gt;
[[File:Example.jpg]]&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download at:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149602</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149602"/>
				<updated>2013-04-11T20:48:25Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Contributions ==&lt;br /&gt;
&lt;br /&gt;
1- The User Privacy Protection Cheat Sheet, written by Kuwait chapter leader Mohammed ALDOUB, discusses methods and techniques in which web developers can protect the privacy, anonymity and identity of their users from the various adversaries.&lt;br /&gt;
&lt;br /&gt;
The cheat sheet is located at: [https://www.owasp.org/index.php/User_Privacy_Protection_Cheat_Sheet User Privacy Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- Presentation by Kuwait chapter leader Mohammed ALDOUB, titled Invaders At the Gates: Last Minute Defenses for Impending Attacks, which can be downloaded here: [[File:InvadersAtTheGates.ppt]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة هنا:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download at:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:InvadersAtTheGates.ppt&amp;diff=149601</id>
		<title>File:InvadersAtTheGates.ppt</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:InvadersAtTheGates.ppt&amp;diff=149601"/>
				<updated>2013-04-11T20:43:54Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: Invaders at the Gates: Last Minute Defenses for Impending Attacks

A talk by Mohammed ALDOUB, OWASP Kuwait chapter leader, in the Cyber Security Summit conference in Prague, Czech Republic, on the 11th of April, 2013.

The presentation discusses the vario&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
A talk by Mohammed ALDOUB, OWASP Kuwait chapter leader, in the Cyber Security Summit conference in Prague, Czech Republic, on the 11th of April, 2013.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149600</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=149600"/>
				<updated>2013-04-11T20:31:12Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
== Presentations ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
قام م. محمد الدوب رئيس فرع أواسب بالكويت بالقاء محاضرة بمؤتمر Cyber Security Summit &lt;br /&gt;
&lt;br /&gt;
في براغ عاصمة التشيك بتاريخ ١١ ابريل ٢٠١٣، تحت عنوان Invaders at the Gates: Last Minute Defenses for Impending Attacks&lt;br /&gt;
&lt;br /&gt;
، وتتكلم المحاضرة عن اساليب الدفاع السريعة ضد الهجمات المفاجئة او عند الحاجة لتأمين الخوادم والشبكات بأسرع وقت ممكن&lt;br /&gt;
&lt;br /&gt;
يمكن تحميل المحاضرة هنا:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
On the 11th of April 2013, Mr. Mohammed ALDOUB (OWASP Kuwait chapter leader) gave a presentation in the Cyber Security Summit conference in Prague, Czech Republic, titled Invaders at the Gates: Last Minute Defenses for Impending Attacks.&lt;br /&gt;
&lt;br /&gt;
The presentation discusses the variou techniques that can be implemented quickly to set up last minute defenses for impending attacks, Tools and techniques for reactive defense and monitoring of live attacks without the need for complicated tools and procedures, as well as techniques and tricks to disrupt live attack attempts and confuse attackers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The presentation is available for download at:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
------------------&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_Privacy_Protection_Cheat_Sheet&amp;diff=144429</id>
		<title>User Privacy Protection Cheat Sheet</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_Privacy_Protection_Cheat_Sheet&amp;diff=144429"/>
				<updated>2013-02-14T23:18:49Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Introduction =&lt;br /&gt;
This OWASP Cheat Sheet introduces mitigation methods that web developers may utilize in order to protect their users from a vast array of&lt;br /&gt;
potential threats and aggressions that might try to undermine their privacy and anonymity. This cheat sheet focuses on privacy and anonymity threats that users might face by using online services, especially in contexts such as social networking and communication platforms. &lt;br /&gt;
&lt;br /&gt;
= Guidelines =&lt;br /&gt;
&lt;br /&gt;
== Strong Cryptography ==&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control. &lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TLS/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
Private data must be encrypted in storage using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage. &lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references: &lt;br /&gt;
&lt;br /&gt;
# [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
# [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
# [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
# [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
# [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to HTTPS, and forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user. &lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agents, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and Man in the Middle Attacks. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it. &lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit: &lt;br /&gt;
&lt;br /&gt;
# [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
# [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
# [http://www.youtube.com/watch?v=zEV3HOuM_Vw OWASP Appsec Tutorial Series - Episode 4: Strict Transport Security]&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of information (usually hashes) for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates/public keys are used for secure communication, and all others will fail, even if the user trusted (implicitly or explicitly) the other certificates/public keys. &lt;br /&gt;
&lt;br /&gt;
Some advantages for pinning are: &lt;br /&gt;
&lt;br /&gt;
* In the event of a CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users. &lt;br /&gt;
* In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
* In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate. &lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following: &lt;br /&gt;
&lt;br /&gt;
# [https://www.owasp.org/index.php/Pinning_Cheat_Sheet OWASP Certificate Pinning Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
# [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
# [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials.&lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account. &lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or invoke triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his/her distressed password. &lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, allowing reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account. &lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be easily discoverable, if at all. An adversary inside a victim's panic mode must not have any way, or as few possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account. &lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from reaching the actual accounts/sensitive data of the victim, as well as prevent the discovery of any existing panic modes for a particular account. &lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to: &lt;br /&gt;
&lt;br /&gt;
# [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see view their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also helps if a user suspects that his/her session details were stolen in a Man-in-the-Middle attack. &lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to: &lt;br /&gt;
&lt;br /&gt;
# [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
== Allow Connections from Anonymity Networks ==&lt;br /&gt;
&lt;br /&gt;
Anonymity networks, such as the Tor Project, give users in tumultuous regions around the world a golden chance to escape surveillance, access information or break censorship barriers. More often than not, activists in troubled regions use such networks to report injustice or send uncensored information to the rest of the world, especially mediums such as social networks, media streaming websites and e-mail providers. &lt;br /&gt;
&lt;br /&gt;
Web developers and network administrators must pursue every avenue to enable users to access services from behind such networks, and any policy made against such anonymity networks need to be carefully re-evaluated with respect to impact on people around the world. &lt;br /&gt;
&lt;br /&gt;
If possible, application developers should try to integrate or enable easy coupling of their applications with these anonymity networks, such as supporting SOCKS proxies or integration libraries (e.g. OnionKit for Android). &lt;br /&gt;
&lt;br /&gt;
For more information about anonymity networks, and the user protections they provide, please refer to: &lt;br /&gt;
&lt;br /&gt;
#  [https://www.torproject.org The Tor Project]&lt;br /&gt;
# [http://www.i2p2.de I2P Network]&lt;br /&gt;
# [https://github.com/guardianproject/OnionKit OnionKit: Boost Network Security and Encryption in your Android Apps]&lt;br /&gt;
&lt;br /&gt;
== Prevent IP Address Leakage ==&lt;br /&gt;
&lt;br /&gt;
Preventing leakage of user IP addresses is of great significance when user protection is in scope. Any application that hosts external 3rd party content, such as avatars, signatures or photo attachments; must take into account the benefits of allowing users to block 3rd-party content from being loaded in the application page. &lt;br /&gt;
&lt;br /&gt;
If it was possible to embed 3rd-party, external domain images, for example, in a user's feed or timeline; an adversary might use it to discover a victim's real IP address by hosting it on his domain and watch for HTTP requests for that image. &lt;br /&gt;
&lt;br /&gt;
Many web applications need user content to operate, and this is completely acceptable as a business process; however web developers are advised to consider giving users the option of blocking external content as a precaution. This applies mainly to social networks and forums, but can also apply to web-based e-mail, where images can be embedded in HTML-formatted e-mails. &lt;br /&gt;
&lt;br /&gt;
A similar issue exists in HTML-formatted emails that contain 3rd party images, however most e-mail clients and providers block loading of 3rd party content by default; giving users better privacy and anonymity protection.&lt;br /&gt;
&lt;br /&gt;
== Honesty &amp;amp; Transparency ==&lt;br /&gt;
&lt;br /&gt;
If the web application cannot provide enough legal or political protections to the user, or if the web application cannot prevent misuse or disclosure of sensitive information such as logs, the truth must be told to the users in a clear understandable form, so that users can make an educated choice about whether or not they should use that particular service. &lt;br /&gt;
&lt;br /&gt;
If it doesn't violate the law, inform users if their information is being requested for removal or investigation by external entities. &lt;br /&gt;
&lt;br /&gt;
Honesty goes a long way towards cultivating a culture of trust between a web application and its users, and it allows many users around the world to weigh their options carefully, preventing harm to users in various contrasting regions around the world. &lt;br /&gt;
&lt;br /&gt;
More insight regarding secure logging can be found at: &lt;br /&gt;
&lt;br /&gt;
# [https://www.owasp.org/index.php/Logging_Cheat_Sheet OWASP Logging Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
= Authors and Primary Editors  =&lt;br /&gt;
&lt;br /&gt;
Mohammed ALDOUB - OWASP Kuwait chapter leader&lt;br /&gt;
&lt;br /&gt;
= Other Cheatsheets =&lt;br /&gt;
&lt;br /&gt;
{{Cheatsheet_Navigation}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Cheatsheets]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_Privacy_Protection_Cheat_Sheet&amp;diff=137019</id>
		<title>User Privacy Protection Cheat Sheet</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_Privacy_Protection_Cheat_Sheet&amp;diff=137019"/>
				<updated>2012-10-04T06:50:56Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= DRAFT CHEAT SHEET - WORK IN PROGRESS =&lt;br /&gt;
= Introduction =&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world. &lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigation methods that web developers need to realize in order to protect their users from a vast array of potential aggressors around the world that might try to undermine users’ privacy and anonymity in order to harass, persecute or hunt them down.&lt;br /&gt;
&lt;br /&gt;
= Scope of Threats =&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on privacy and anonymity threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers. &lt;br /&gt;
&lt;br /&gt;
= Guidelines =&lt;br /&gt;
&lt;br /&gt;
== Strong Cryptography ==&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control. &lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage. &lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references: &lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user. &lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agents, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and Man in the Middle Attacks. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it. &lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit: &lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are: &lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users. &lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate. &lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following: &lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials. Many times such threats around the world are accompanied by violence, blackmail or even imprisonment. &lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account. &lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his distressed password. &lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, and allow reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account. &lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be discoverable. An adversary inside a victim's panic mode must not have any way, or as little possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account. &lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from figuring out the truth about victim accounts and data, as well as the existence of panic modes for a particular account. &lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to: &lt;br /&gt;
&lt;br /&gt;
1- [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also help if a user suspects his session details were stolen in a Man-in-the-Middle attack. &lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to: &lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
== Allow Connections from Anonymity Networks ==&lt;br /&gt;
&lt;br /&gt;
Anonymity networks, such as the Tor Project, give users in tumultuous regions around the world a golden chance to escape surveillance, access information or the ability to break censorship barriers. More often than not, activists in troubled regions use such networks to report injustice or send uncensored information to the rest of the world, especially mediums such as social networks, media streaming websites and e-mail providers. &lt;br /&gt;
&lt;br /&gt;
Web developers and network administrators must pursue every avenue to enable users to access services from behind such networks, and any policy made against such anonymity networks need to be carefully re-evaluated with respect to impact on people around the world. &lt;br /&gt;
&lt;br /&gt;
If possible, application developers should try to integrate or enable easy coupling of their applications with these anonymity networks, such as supporting SOCKS proxies or integration libraries (e.g. ORLib for Android). &lt;br /&gt;
&lt;br /&gt;
For more information about anonymity networks, and the user protections they provide, please refer to: &lt;br /&gt;
&lt;br /&gt;
1- [https://www.torproject.org The Tor Project]&lt;br /&gt;
&lt;br /&gt;
2- [http://www.i2p2.de I2P Network]&lt;br /&gt;
&lt;br /&gt;
3- [https://guardianproject.info/code/orlib/ ORLib: Tor-ify Your App]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Prevent IP Address Leakage ==&lt;br /&gt;
&lt;br /&gt;
Preventing leakage of user IP address is of great significance when user protection is in scope. Any application that hosts external 3rd party content, such as avatars, signatures or photo attachments; must take into account the benefits of allowing users to block 3rd-party content from being loaded in the application page. &lt;br /&gt;
&lt;br /&gt;
If it was possible to embed 3rd-party, external domain images, for example, in a user's feed or timeline; an adversary might use it to discover a victim's real IP address by hosting it on his domain and watch for HTTP requests for that image. &lt;br /&gt;
&lt;br /&gt;
Many web applications need user content to operate, and this is completely acceptable as a business process; however web developers are advised to consider giving users the option of blocking external content as a precaution. This applies mainly to social networks and forums, but can also apply to web-based e-mail, where images can be embedded in HTML-formatted e-mails. &lt;br /&gt;
&lt;br /&gt;
== Honesty &amp;amp; Transparency ==&lt;br /&gt;
&lt;br /&gt;
If the web application cannot provide enough legal or political protections to the user, or if the web application cannot prevent misuse or disclosure of sensitive information such as logs, the truth must be told to the users in a clear understandable form, so that users can make an educated choice about whether or not they should use a particular service. &lt;br /&gt;
&lt;br /&gt;
If it doesn't violate the law, inform users if their information is being requested for removal or investigation by external entities. &lt;br /&gt;
&lt;br /&gt;
Honesty goes a long way towards cultivating a culture of trust between a web application and its users, and it allows many users around the world to weigh their options carefully, preventing harm to users in various contrasting regions around the world. &lt;br /&gt;
&lt;br /&gt;
More insight regarding secure logging can be found at: &lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Logging_Cheat_Sheet OWASP Logging Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Authors and Primary Editors  =&lt;br /&gt;
&lt;br /&gt;
Mohammed ALDOUB - OWASP Kuwait chapter leader&lt;br /&gt;
&lt;br /&gt;
= Other Cheatsheets =&lt;br /&gt;
&lt;br /&gt;
{{Cheatsheet_Navigation}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Cheatsheets]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=136751</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=136751"/>
				<updated>2012-09-29T10:19:57Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=136750</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=136750"/>
				<updated>2012-09-29T10:18:57Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
,&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps?q=Kuwait+Information+Technology+Society,+Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;hl=en&amp;amp;ll=29.323822,48.010683&amp;amp;spn=0.018671,0.038538&amp;amp;sll=29.32385,48.010318&amp;amp;sspn=0.018671,0.038538&amp;amp;oq=Kuwait+Information+&amp;amp;hq=Kuwait+Information+Technology+Society,&amp;amp;hnear=Al-Rawda,+Al+Asimah,+Kuwait&amp;amp;t=m&amp;amp;z=15 link Click Here for Google Maps location]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=136299</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=136299"/>
				<updated>2012-09-22T18:03:40Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== User Privacy and Anonymity Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world. &lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors around the world that might try to undermine users’ privacy and anonymity in order to harass, persecute or hunt them down.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on privacy and anonymity threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Strong Cryptography ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it.&lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are:&lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users.&lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate.&lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials. Many times such threats around the world are accompanied by violence, blackmail or even imprisonment.&lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account.&lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his distressed password.&lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, and allow reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account.&lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be discoverable. An adversary inside a victim's panic mode must not have any way, or as little possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
&lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account.&lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from figuring out the truth about victim accounts and data, as well as the existence of panic modes for a particular account.&lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also help if a user suspects his session details were stolen in a Man-in-the-Middle attack.&lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Allow Connections from Anonymity Networks ==&lt;br /&gt;
&lt;br /&gt;
Anonymity networks, such as the Tor Project, give users in tumultuous regions around the world a golden chance to escape surveillance, access information or the ability to break censorship barriers. More often than not, activists in troubled regions use such networks to report injustice or send uncensored information to the rest of the world, especially mediums such as social networks, media streaming websites and e-mail providers.&lt;br /&gt;
&lt;br /&gt;
Web developers and network administrators must pursue every avenue to enable users to access services from behind such networks, and any policy made against such anonymity networks need to be carefully re-evaluated with respect to impact on people around the world.&lt;br /&gt;
&lt;br /&gt;
If possible, application developers should try to integrate or enable easy coupling of their applications with these anonymity networks, such as supporting SOCKS proxies or integration libraries (e.g. ORLib for Android).&lt;br /&gt;
&lt;br /&gt;
For more information about anonymity networks, and the user protections they provide, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.torproject.org The Tor Project]&lt;br /&gt;
&lt;br /&gt;
2- [http://www.i2p2.de I2P Network]&lt;br /&gt;
&lt;br /&gt;
3- [https://guardianproject.info/code/orlib/ ORLib: Tor-ify Your App]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Prevent IP Address Leakage ==&lt;br /&gt;
&lt;br /&gt;
Preventing leakage of user IP address is of great significance when user protection is in scope. Any application that hosts external 3rd party content, such as avatars, signatures or photo attachments; must take into account the benefits of allowing users to block 3rd-party content from being loaded in the application page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If it was possible to embed 3rd-party, external domain images, for example, in a user's feed or timeline; an adversary might use it to discover a victim's real IP address by hosting it on his domain and watch for HTTP requests for that image. &lt;br /&gt;
&lt;br /&gt;
Many web applications need user content to operate, and this is completely acceptable as a business process; however web developers are advised to consider giving users the option of blocking external content as a precaution. This applies mainly to social networks and forums, but can also apply to web-based e-mail, where images can be embedded in HTML-formatted e-mails.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Honesty &amp;amp; Transparency ==&lt;br /&gt;
&lt;br /&gt;
If the web application cannot provide enough legal or political protections to the user, or if the web application cannot prevent misuse or disclosure of sensitive information such as logs, the truth must be told to the users in a clear understandable form, so that users can make an educated choice about whether or not they should use a particular service.&lt;br /&gt;
&lt;br /&gt;
If it doesn't violate the law, inform users if their information is being requested for removal or investigation by external entities.&lt;br /&gt;
&lt;br /&gt;
Honesty goes a long way towards cultivating a culture of trust between a web application and its users, and it allows many users around the world to weigh their options carefully, preventing harm to users in various contrasting regions around the world.&lt;br /&gt;
&lt;br /&gt;
More insight regarding secure logging can be found at:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Logging_Cheat_Sheet OWASP Logging Cheat Sheet]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=136298</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=136298"/>
				<updated>2012-09-22T17:53:34Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Strong Cryptography ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it.&lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are:&lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users.&lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate.&lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials. Many times such threats around the world are accompanied by violence, blackmail or even imprisonment.&lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account.&lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his distressed password.&lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, and allow reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account.&lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be discoverable. An adversary inside a victim's panic mode must not have any way, or as little possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
&lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account.&lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from figuring out the truth about victim accounts and data, as well as the existence of panic modes for a particular account.&lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also help if a user suspects his session details were stolen in a Man-in-the-Middle attack.&lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Allow Connections from Anonymity Networks ==&lt;br /&gt;
&lt;br /&gt;
Anonymity networks, such as the Tor Project, give users in tumultuous regions around the world a golden chance to escape surveillance, access information or the ability to break censorship barriers. More often than not, activists in troubled regions use such networks to report injustice or send uncensored information to the rest of the world, especially mediums such as social networks, media streaming websites and e-mail providers.&lt;br /&gt;
&lt;br /&gt;
Web developers and network administrators must pursue every avenue to enable users to access services from behind such networks, and any policy made against such anonymity networks need to be carefully re-evaluated with respect to impact on people around the world.&lt;br /&gt;
&lt;br /&gt;
If possible, application developers should try to integrate or enable easy coupling of their applications with these anonymity networks, such as supporting SOCKS proxies or integration libraries (e.g. ORLib for Android).&lt;br /&gt;
&lt;br /&gt;
For more information about anonymity networks, and the user protections they provide, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.torproject.org The Tor Project]&lt;br /&gt;
&lt;br /&gt;
2- [http://www.i2p2.de I2P Network]&lt;br /&gt;
&lt;br /&gt;
3- [https://guardianproject.info/code/orlib/ ORLib: Tor-ify Your App]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Prevent IP Address Leakage ==&lt;br /&gt;
&lt;br /&gt;
Preventing leakage of user IP address is of great significance when user protection is in scope. Any application that hosts external 3rd party content, such as avatars, signatures or photo attachments; must take into account the benefits of allowing users to block 3rd-party content from being loaded in the application page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If it was possible to embed 3rd-party, external domain images, for example, in a user's feed or timeline; an adversary might use it to discover a victim's real IP address by hosting it on his domain and watch for HTTP requests for that image. &lt;br /&gt;
&lt;br /&gt;
Many web applications need user content to operate, and this is completely acceptable as a business process; however web developers are advised to consider giving users the option of blocking external content as a precaution. This applies mainly to social networks and forums, but can also apply to web-based e-mail, where images can be embedded in HTML-formatted e-mails.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Honesty &amp;amp; Transparency ==&lt;br /&gt;
&lt;br /&gt;
If the web application cannot provide enough legal or political protections to the user, or if the web application cannot prevent misuse or disclosure of sensitive information such as logs, the truth must be told to the users in a clear understandable form, so that users can make an educated choice about whether or not they should use a particular service.&lt;br /&gt;
&lt;br /&gt;
If it doesn't violate the law, inform users if their information is being requested for removal or investigation by external entities.&lt;br /&gt;
&lt;br /&gt;
Honesty goes a long way towards cultivating a culture of trust between a web application and its users, and it allows many users around the world to weigh their options carefully, preventing harm to users in various contrasting regions around the world.&lt;br /&gt;
&lt;br /&gt;
More insight regarding secure logging can be found at:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Logging_Cheat_Sheet OWASP Logging Cheat Sheet]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=135656</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=135656"/>
				<updated>2012-09-11T16:07:58Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Meeting Details تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
,&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=135655</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=135655"/>
				<updated>2012-09-11T16:07:06Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== تفاصيل اللقاءات ==&lt;br /&gt;
&lt;br /&gt;
== Meeting Details ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 '''First Meeting Location مكان اللقاء الأول'''&lt;br /&gt;
&lt;br /&gt;
مرحبا بكم بأول اجتماع لأواسب الكويت!&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
'''Date التاريخ'''&lt;br /&gt;
٢٩ من سبتمبر ٢٠١٢، الساعة الثامنة و النصف مساءاً&lt;br /&gt;
September the 29th, 2012. At 8:30 PM&lt;br /&gt;
&lt;br /&gt;
'''Agenda الأجندة'''&lt;br /&gt;
&lt;br /&gt;
التعريف عن منظمة أواسب و أهدافها و مشاريعها و عضويتها.&lt;br /&gt;
نقاش بسيط عن وضع أمن المواقع بالكويت&lt;br /&gt;
&lt;br /&gt;
Introduction to OWASP, its goals, projects and membership.&lt;br /&gt;
Brief discussion about the state of web security in Kuwait.&lt;br /&gt;
&lt;br /&gt;
'''Location المكان'''&lt;br /&gt;
&lt;br /&gt;
الجمعية الكويتية لتقنية المعلومات، منطقة الروضة&lt;br /&gt;
Kuwait Information Technology Society (KITS), Rawda area&lt;br /&gt;
&lt;br /&gt;
الروضة – قطعة 3 – ش ابوحيان التوحيدي – جادة 37 – منزل رقم 20 هاتف :22529303 فاكس : 22527986&lt;br /&gt;
,&lt;br /&gt;
&amp;lt;googlemap version=&amp;quot;0.9&amp;quot; lat=&amp;quot;29.32385&amp;quot; lon=&amp;quot;48.010318&amp;quot; zoom=&amp;quot;18&amp;quot;&amp;gt;&lt;br /&gt;
29.32385, 48.010318&lt;br /&gt;
&amp;lt;/googlemap&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134224</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134224"/>
				<updated>2012-08-12T21:40:30Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Strong Cryptography ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it.&lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are:&lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users.&lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate.&lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials. Many times such threats around the world are accompanied by violence, blackmail or even imprisonment.&lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account.&lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his distressed password.&lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, and allow reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account.&lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be discoverable. An adversary inside a victim's panic mode must not have any way, or as little possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
&lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account.&lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from figuring out the truth about victim accounts and data, as well as the existence of panic modes for a particular account.&lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also help if a user suspects his session details were stolen in a Man-in-the-Middle attack.&lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Allow Connections from Anonymity Networks ==&lt;br /&gt;
&lt;br /&gt;
Anonymity networks, such as the Tor Project, give users in tumultuous regions around the world a golden chance to escape surveillance, to access information or to break censorship barriers. More often than not, activists in troubled regions use such networks to report injustice or send uncensored information to the rest of the world, especially mediums such as social networks, media streaming websites and e-mail providers.&lt;br /&gt;
&lt;br /&gt;
Web developers and network administrators must pursue every avenue to enable users to access services from behind such networks, and any policy made against such anonymity networks need to be carefully re-evaluated with respect to impact on people around the world.&lt;br /&gt;
&lt;br /&gt;
For more information about anonymity networks, and the user protections they provide, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.torproject.org The Tor Project]&lt;br /&gt;
&lt;br /&gt;
2- [http://www.i2p2.de I2P Network]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Prevent IP Address Leakage ==&lt;br /&gt;
&lt;br /&gt;
Preventing leakage of user IP address is of great significance when user protection is in scope. Any application that hosts external 3rd party content, such as avatars or signatures, must take into account the benefits of allowing users to block 3rd-party content from being loaded in the application page.&lt;br /&gt;
&lt;br /&gt;
If it was possible to embed 3rd-party, external domain images, for example, in a user's feed or timeline; an adversary might use it to discover a victim's real IP address by hosting it on his domain and watch for HTTP requests for that image. &lt;br /&gt;
&lt;br /&gt;
Many web applications need user content to operate, and this is completely acceptable as a business process; however web developers are advised to consider giving users the option of blocking external content as a precaution. This applies mainly to social networks and forums, but can also apply to web-based e-mail, where images can be embedded in HTML-formatted e-mails.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Honesty &amp;amp; Transparency ==&lt;br /&gt;
&lt;br /&gt;
If the web application cannot provide enough legal or political protections to the user, or if the web application cannot prevent misuse or disclosure of sensitive information such as logs, the truth must be told to the users in a clear understandable form, so that users can make an educated choice about whether or not they should use a particular service.&lt;br /&gt;
&lt;br /&gt;
Honesty goes a long way towards cultivating a culture of trust between a web application and its users, and it allows many users around the world to weigh their options carefully, preventing harm to users in various contrasting regions around the world.&lt;br /&gt;
&lt;br /&gt;
More insight regarding secure logging can be found at:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Logging_Cheat_Sheet OWASP Logging Cheat Sheet]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134223</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134223"/>
				<updated>2012-08-12T21:38:30Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Strong Cryptography ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it.&lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are:&lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users.&lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate.&lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials. Many times such threats around the world are accompanied by violence, blackmail or even imprisonment.&lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account.&lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his distressed password.&lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, and allow reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account.&lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be discoverable. An adversary inside a victim's panic mode must not have any way, or as little possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
&lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account.&lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from figuring out the truth about victim accounts and data, as well as the existence of panic modes for a particular account.&lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also help if a user suspects his session details were stolen in a Man-in-the-Middle attack.&lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Allow Connections from Anonymity Networks ==&lt;br /&gt;
&lt;br /&gt;
Anonymity networks, such as the Tor Project, give users in tumultuous regions around the world a golden chance to escape surveillance, to access information or to break censorship barriers. More often than not, activists in troubled regions use such networks to report injustice or send uncensored information to the rest of the world, especially mediums such as social networks, media streaming websites and e-mail providers.&lt;br /&gt;
&lt;br /&gt;
Web developers and network administrators must pursue every avenue to enable users to access services from behind such networks, and any policy made against such anonymity networks need to be carefully re-evaluated with respect to impact on people around the world.&lt;br /&gt;
&lt;br /&gt;
For more information about anonymity networks, and the user protections they provide, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.torproject.org The Tor Project]&lt;br /&gt;
&lt;br /&gt;
2- [http://www.i2p2.de I2P Network]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Prevent IP Address Leakage ==&lt;br /&gt;
&lt;br /&gt;
Preventing leakage of user IP address is of great significance when user protection is in scope. Any application that hosts external 3rd party content, such as avatars or signatures, must take into account the benefits of allowing users to block 3rd-party content from being loaded in the application page.&lt;br /&gt;
&lt;br /&gt;
If it was possible to embed 3rd-party, external domain images, for example, in a user's feed or timeline; an adversary might use it to discover a victim's real IP address by hosting it on his domain and watch for HTTP requests for that image. &lt;br /&gt;
&lt;br /&gt;
Many web applications need user content to operate, and this is completely acceptable as a business process; however web developers are advised to consider giving users the option of blocking external content as a precaution. This applies mainly to social networks and forums, but can also apply to web-based e-mail, where images can be embedded in HTML-formatted e-mails.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Honesty &amp;amp; Transparency ==&lt;br /&gt;
&lt;br /&gt;
If the web application cannot provide enough legal or political protections to the user, or if the web application cannot prevent misuse or disclosure of sensitive information such as logs, the truth must be told to the users in a clear understandable form, so that users can make an educated choice about whether or not they should use a particular service.&lt;br /&gt;
&lt;br /&gt;
Honesty goes a long way towards cultivating a culture of trust between a web application and its users, and it allows many users around the world to weigh their options carefully, preventing harm to users in various contrasting regions around the world.&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134222</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134222"/>
				<updated>2012-08-12T21:15:55Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Strong Cryptography ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it.&lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are:&lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users.&lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate.&lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials. Many times such threats around the world are accompanied by violence, blackmail or even imprisonment.&lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account.&lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his distressed password.&lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, and allow reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account.&lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be discoverable. An adversary inside a victim's panic mode must not have any way, or as little possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
&lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account.&lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from figuring out the truth about victim accounts and data, as well as the existence of panic modes for a particular account.&lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also help if a user suspects his session details were stolen in a Man-in-the-Middle attack.&lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Allow Connections from Anonymity Networks ==&lt;br /&gt;
&lt;br /&gt;
Anonymity networks, such as the Tor Project, give users in tumultuous regions around the world a golden chance to escape surveillance, to access information or to break censorship barriers. More often than not, activists in troubled regions use such networks to report injustice or send uncensored information to the rest of the world, especially mediums such as social networks, media streaming websites and e-mail providers.&lt;br /&gt;
&lt;br /&gt;
Web developers and network administrators must pursue every avenue to enable users to access services from behind such networks, and any policy made against such anonymity networks need to be carefully re-evaluated with respect to impact on people around the world.&lt;br /&gt;
&lt;br /&gt;
For more information about anonymity networks, and the user protections they provide, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.torproject.org The Tor Project]&lt;br /&gt;
&lt;br /&gt;
2- [http://www.i2p2.de I2P Network]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134221</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134221"/>
				<updated>2012-08-12T21:15:14Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
'''1- Strong Cryptography:&lt;br /&gt;
'''&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it.&lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are:&lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users.&lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate.&lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials. Many times such threats around the world are accompanied by violence, blackmail or even imprisonment.&lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account.&lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his distressed password.&lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, and allow reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account.&lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be discoverable. An adversary inside a victim's panic mode must not have any way, or as little possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
&lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account.&lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from figuring out the truth about victim accounts and data, as well as the existence of panic modes for a particular account.&lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also help if a user suspects his session details were stolen in a Man-in-the-Middle attack.&lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Allow Connections from Anonymity Networks ==&lt;br /&gt;
&lt;br /&gt;
Anonymity networks, such as the Tor Project, give users in tumultuous regions around the world a golden chance to escape surveillance, to access information or to break censorship barriers. More often than not, activists in troubled regions use such networks to report injustice or send uncensored information to the rest of the world, especially mediums such as social networks, media streaming websites and e-mail providers.&lt;br /&gt;
&lt;br /&gt;
Web developers and network administrators must pursue every avenue to enable users to access services from behind such networks, and any policy made against such anonymity networks need to be carefully re-evaluated with respect to impact on people around the world.&lt;br /&gt;
&lt;br /&gt;
For more information about anonymity networks, and the user protections they provide, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.torproject.org The Tor Project]&lt;br /&gt;
&lt;br /&gt;
2- [http://www.i2p2.de I2P Network]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134220</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134220"/>
				<updated>2012-08-12T21:14:50Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
'''1- Strong Cryptography:&lt;br /&gt;
'''&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it.&lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are:&lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users.&lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate.&lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials. Many times such threats around the world are accompanied by violence, blackmail or even imprisonment.&lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account.&lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his distressed password.&lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, and allow reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account.&lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be discoverable. An adversary inside a victim's panic mode must not have any way, or as little possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
&lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account.&lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from figuring out the truth about victim accounts and data, as well as the existence of panic modes for a particular account.&lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also help if a user suspects his session details were stolen in a Man-in-the-Middle attack.&lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Allow Connections from Anonymity Networks ==&lt;br /&gt;
&lt;br /&gt;
Anonymity networks, such as the Tor Project, give users in tumultuous regions around the world a golden chance to escape surveillance, to access information or to break censorship barriers. More often than not, activists in troubled regions use such networks to report injustice or send uncensored information to the rest of the world, especially mediums such as social networks, media streaming websites and e-mail providers.&lt;br /&gt;
&lt;br /&gt;
Web developers and network administrators must pursue every avenue to enable users to access services from behind such networks, and any policy made against such anonymity networks need to be carefully re-evaluated with respect to impact on people around the world.&lt;br /&gt;
&lt;br /&gt;
For more information about anonymity networks, and the user protections they provide, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.torproject.org The Tor Project]&lt;br /&gt;
2- [http://www.i2p2.de I2P Network]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134219</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134219"/>
				<updated>2012-08-12T21:02:59Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
'''1- Strong Cryptography:&lt;br /&gt;
'''&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it.&lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are:&lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users.&lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate.&lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Panic Modes ==&lt;br /&gt;
&lt;br /&gt;
A panic mode is a mode that threatened users can refer to when they fall under direct threat to disclose account credentials. Many times such threats around the world are accompanied by violence, blackmail or even imprisonment.&lt;br /&gt;
&lt;br /&gt;
Giving users the ability to create a panic mode can help them survive these threats, especially in tumultuous regions around the world. Unfortunately many users around the world are subject to types of threats that most web developers do not know of or take into account.&lt;br /&gt;
&lt;br /&gt;
Examples of panic modes are modes where distressed users can delete their data upon threat, log into fake inboxes/accounts/systems, or triggers to backup/upload/hide sensitive data. &lt;br /&gt;
&lt;br /&gt;
The appropriate panic mode to implement differs depending on the application type. A disk encryption software such as TrueCrypt might implement a panic mode that starts up a fake system partition if the user entered his distressed password.&lt;br /&gt;
&lt;br /&gt;
E-mail providers might implement a panic mode that hides predefined sensitive emails or contacts, and allow reading innocent e-mail messages only, usually as defined by the user, while preventing the panic mode from overtaking the actual account.&lt;br /&gt;
&lt;br /&gt;
An important note about panic modes is that they must not be discoverable. An adversary inside a victim's panic mode must not have any way, or as little possibilities as possible, of finding out the truth. This means that once inside a panic mode, most non-sensitive normal operations must be allowed to continue (such as sending or receiving email), and that further panic modes must be possible to create from inside the original panic mode (If the adversary tried to create a panic mode on a victim's panic mode and failed, the adversary would know he/she was already inside a panic mode, and might attempt to hurt the victim). &lt;br /&gt;
&lt;br /&gt;
Another solution would be to prevent panic modes from being generated from the user account, and instead making it a bit harder to spoof by adversaries. For example it could be only created Out Of Band, and adversaries must have no way to know a panic mode already exists for that particular account.&lt;br /&gt;
&lt;br /&gt;
The implementation of a panic mode must always aim to confuse adversaries and prevent them from figuring out the truth about victim accounts and data, as well as the existence of panic modes for a particular account.&lt;br /&gt;
&lt;br /&gt;
For more details regarding TrueCrypt's hidden operating system mode, please refer to:&lt;br /&gt;
&lt;br /&gt;
1- [http://www.truecrypt.org/docs/?s=hidden-operating-system TrueCrypt Hidden Operating System]&lt;br /&gt;
&lt;br /&gt;
== Remote Session Invalidation ==&lt;br /&gt;
&lt;br /&gt;
In case user equipment is lost, stolen or confiscated, or under suspicion of cookie theft; it might be very beneficial for users to able to see their current online sessions and disconnect/invalidate any suspicious lingering sessions, especially ones that belong to stolen or confiscated devices. Remote session invalidation can also help if a user suspects his session details were stolen in a Man-in-the-Middle attack.&lt;br /&gt;
&lt;br /&gt;
For details regarding session management, please refer to:&lt;br /&gt;
1- [https://www.owasp.org/index.php/Session_Management_Cheat_Sheet OWASP Session Management Cheat Sheet]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134017</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134017"/>
				<updated>2012-08-07T22:19:16Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
'''1- Strong Cryptography:&lt;br /&gt;
'''&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
If it is impractical to force HSTS on all users, web developers should at least give users the choice to enable it if they wish to make use of it.&lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Digital Certificate Pinning ==&lt;br /&gt;
&lt;br /&gt;
Certificate Pinning is the practice of hardcoding or storing a pre-defined set of hashes for digital certificates/public keys in the user agent (be it web browser, mobile app or browser plugin) such that only the predefined certificates are used for secured communication, and any other certificate will fail, even if the user trusted (implicitly or explicitly) the other certificates. &lt;br /&gt;
&lt;br /&gt;
Some advantages for certificate pinning are:&lt;br /&gt;
&lt;br /&gt;
- In the event of CA compromise, in which a compromised CA trusted by a user can issue certificates for any domain, allowing evil perpetrators to eavesdrop on users.&lt;br /&gt;
&lt;br /&gt;
- In environments where users are forced to accept a potentially-malicious root CA, such as corporate environments or national PKI schemes. &lt;br /&gt;
&lt;br /&gt;
- In applications where the target demographic may not understand certificate warnings, and is likely to just allow any invalid certificate.&lt;br /&gt;
&lt;br /&gt;
For details regarding certificate pinning, please refer to the following:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.ietf.org/id/draft-ietf-websec-key-pinning-02.txt Public Key Pinning Extension for HTTP draft-ietf-websec-key-pinning-02]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/images/4/4b/OWASP_defending-MITMA_APAC2012.pdf Securing the SSL channel against man-in-the-middle attacks: Future technologies - HTTP Strict Transport Security and and Pinning of Certs, by Tobias Gondrom]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134011</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134011"/>
				<updated>2012-08-07T21:13:09Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Welcome to ''OWASP''!'''&lt;br /&gt;
We hope you will contribute much and well.&lt;br /&gt;
You will probably want to read the [[Help:Contents|help pages]].&lt;br /&gt;
Again, welcome and have fun! [[User:KateHartmann|KateHartmann]] 11:26, 31 May 2012 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Testing ==&lt;br /&gt;
&lt;br /&gt;
Hello, I'm testing. If you see this, please say Hello World&lt;br /&gt;
&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
'''1- Strong Cryptography:&lt;br /&gt;
'''&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Support HTTP Strict Transport Security ==&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an HTTP header set by the server indicating to the user agent that only secure (HTTPS) connections are accepted, prompting the user agent to change all insecure HTTP links to secure HTTPS ones, and also forcing the compliant user agent to fail-safe by refusing any TLS/SSL connection that is not trusted by the user.&lt;br /&gt;
&lt;br /&gt;
HSTS has average support on popular user agent, such as Mozilla Firefox and Google Chrome. Nevertheless, it remains very useful for users who are in consistent fear of spying and [https://www.owasp.org/index.php/Man-in-the-middle_attack Man in the Middle Attacks]. &lt;br /&gt;
&lt;br /&gt;
For more details regarding HSTS, please visit:&lt;br /&gt;
&lt;br /&gt;
1- [https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security HTTP Strict Transport Security in Wikipedia]&lt;br /&gt;
&lt;br /&gt;
2- [https://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-11 IETF Draft for HSTS]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134010</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=134010"/>
				<updated>2012-08-07T20:59:33Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Welcome to ''OWASP''!'''&lt;br /&gt;
We hope you will contribute much and well.&lt;br /&gt;
You will probably want to read the [[Help:Contents|help pages]].&lt;br /&gt;
Again, welcome and have fun! [[User:KateHartmann|KateHartmann]] 11:26, 31 May 2012 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Testing ==&lt;br /&gt;
&lt;br /&gt;
Hello, I'm testing. If you see this, please say Hello World&lt;br /&gt;
&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
'''1- Strong Cryptography:&lt;br /&gt;
'''&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the use of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms with increasing work factors, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit, developers must use and adhere to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only, informative and clear warnings to users, as well as sufficient key lengths. &lt;br /&gt;
&lt;br /&gt;
Private data must be encrypted in storage as well, using keys with sufficient lengths and under strict access conditions, both technical and procedural. User credentials must be hashed regardless of whether or not they are encrypted in storage.&lt;br /&gt;
&lt;br /&gt;
For detailed guides about strong cryptography and best practices, read the following OWASP references:&lt;br /&gt;
&lt;br /&gt;
1- [https://www.owasp.org/index.php/Cryptographic_Storage_Cheat_Sheet Cryptographic Storage Cheat Sheet]&lt;br /&gt;
2- [https://www.owasp.org/index.php/Authentication_Cheat_Sheet Authentication Cheat Sheet]&lt;br /&gt;
3- [https://www.owasp.org/index.php/Transport_Layer_Protection_Cheat_Sheet Transport Layer Protection Cheat Sheet]&lt;br /&gt;
4- [https://www.owasp.org/index.php/Guide_to_Cryptography Guide to Cryptography]&lt;br /&gt;
5- [https://www.owasp.org/index.php/Testing_for_SSL-TLS_%28OWASP-CM-001%29 Testing for TLS/SSL]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=133915</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=133915"/>
				<updated>2012-08-06T08:40:35Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: /* User Legal and Political Protection Cheat Sheet */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Welcome to ''OWASP''!'''&lt;br /&gt;
We hope you will contribute much and well.&lt;br /&gt;
You will probably want to read the [[Help:Contents|help pages]].&lt;br /&gt;
Again, welcome and have fun! [[User:KateHartmann|KateHartmann]] 11:26, 31 May 2012 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Testing ==&lt;br /&gt;
&lt;br /&gt;
Hello, I'm testing. If you see this, please say Hello World&lt;br /&gt;
&lt;br /&gt;
== User Legal and Political Protection Cheat Sheet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The political and legal impact of online activities has been rising significantly over the years, with users now able to take down entire governments and change legislation using online services and social networking. This fact puts into focus the grave danger users are getting introduced to by using these online services, especially in oppressive regions around the world.&lt;br /&gt;
&lt;br /&gt;
This OWASP Cheat Sheet introduces risks and mitigations that web developers need to realize in order to protect their users from a vast array of potential aggressors, including oppressive governments and organized crime rings around the world.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Scope of Threats ==&lt;br /&gt;
&lt;br /&gt;
An array of potential threats surrounds online users, and this cheat sheet focuses on political and legal threats that users might face by using these online services, especially social networking and communication platforms. The various reports of imprisonments and even execution for users in some parts of the world simply for using online services must be taken seriously by web developers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Guidelines ==&lt;br /&gt;
&lt;br /&gt;
'''1- Strong Cryptography:&lt;br /&gt;
'''&lt;br /&gt;
&lt;br /&gt;
Any online platform that handles user identities, private information or communications must be secured with the usage of strong cryptography. User communications must be encrypted in transit and storage. User secrets such as passwords must also be protected using strong, collision-resistant hashing algorithms, in order to greatly mitigate the risks of exposed credentials as well as proper integrity control.&lt;br /&gt;
&lt;br /&gt;
To protect data in transit,  while adhering to TSL/SSL best practices such as verified certificates, adequately protected private keys, usage of strong ciphers only.&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Global_Chapter_Committee_-_Application_10&amp;diff=133346</id>
		<title>Global Chapter Committee - Application 10</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Global_Chapter_Committee_-_Application_10&amp;diff=133346"/>
				<updated>2012-07-23T20:42:13Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: Undo revision 133345 by Mohammed ALDOUB (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[How to Join a Committee|Click here to return to 'How to Join a Committee' page]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
{| style=&amp;quot;width:100%&amp;quot; border=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
 ! colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; style=&amp;quot;background:#4058A0; color:white&amp;quot;|&amp;lt;font color=&amp;quot;white&amp;quot;&amp;gt;'''COMMITTEE APPLICATION FORM''' &lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:25%; background:#7B8ABD&amp;quot; align=&amp;quot;center&amp;quot;|'''Applicant's Name'''&lt;br /&gt;
 | colspan=&amp;quot;1&amp;quot; style=&amp;quot;width:85%; background:#cccccc&amp;quot; align=&amp;quot;left&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;Add here.&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:25%; background:#7B8ABD&amp;quot; align=&amp;quot;center&amp;quot;| '''Current and past OWASP Roles''' &lt;br /&gt;
 | colspan=&amp;quot;1&amp;quot; style=&amp;quot;width:85%; background:#cccccc&amp;quot; align=&amp;quot;left&amp;quot;|List here.&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:25%; background:#7B8ABD&amp;quot; align=&amp;quot;center&amp;quot;| '''Committee Applying for''' &lt;br /&gt;
 | colspan=&amp;quot;1&amp;quot; style=&amp;quot;width:85%; background:#cccccc&amp;quot; align=&amp;quot;left&amp;quot;|Global Chapter Committee&lt;br /&gt;
 |}&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
Please be aware that for an application to be considered by the board, '''you MUST have 5 recommendations'''.  &lt;br /&gt;
An incomplete application will not be considered for vote.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
{| style=&amp;quot;width:100%&amp;quot; border=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
 ! colspan=&amp;quot;8&amp;quot; align=&amp;quot;center&amp;quot; style=&amp;quot;background:#4058A0; color:white&amp;quot;|&amp;lt;font color=&amp;quot;white&amp;quot;&amp;gt;'''COMMITTEE RECOMMENDATIONS''' &lt;br /&gt;
 |- &lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:white; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;&lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:#7B8ABD; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;'''Who Recommends/Name''' &lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:#7B8ABD; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;'''Role in OWASP'''&lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:#7B8ABD; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;'''Recommendation Content''' &lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''1'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''2'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''3'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''4'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''5'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |}&lt;br /&gt;
----&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Global_Chapter_Committee_-_Application_10&amp;diff=133345</id>
		<title>Global Chapter Committee - Application 10</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Global_Chapter_Committee_-_Application_10&amp;diff=133345"/>
				<updated>2012-07-23T20:35:12Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[How to Join a Committee|Click here to return to 'How to Join a Committee' page]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
{| style=&amp;quot;width:100%&amp;quot; border=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
 ! colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; style=&amp;quot;background:#4058A0; color:white&amp;quot;|&amp;lt;font color=&amp;quot;white&amp;quot;&amp;gt;'''COMMITTEE APPLICATION FORM''' &lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:25%; background:#7B8ABD&amp;quot; align=&amp;quot;center&amp;quot;|'''Applicant's Name'''&lt;br /&gt;
 | colspan=&amp;quot;1&amp;quot; style=&amp;quot;width:85%; background:#cccccc&amp;quot; align=&amp;quot;left&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;Mohammed ALDOUB&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:25%; background:#7B8ABD&amp;quot; align=&amp;quot;center&amp;quot;| '''Current and past OWASP Roles''' &lt;br /&gt;
 | colspan=&amp;quot;1&amp;quot; style=&amp;quot;width:85%; background:#cccccc&amp;quot; align=&amp;quot;left&amp;quot;|Kuwait chapter leader, I also know Arabic, so I can help.&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:25%; background:#7B8ABD&amp;quot; align=&amp;quot;center&amp;quot;| '''Committee Applying for''' &lt;br /&gt;
 | colspan=&amp;quot;1&amp;quot; style=&amp;quot;width:85%; background:#cccccc&amp;quot; align=&amp;quot;left&amp;quot;|Global Chapter Committee&lt;br /&gt;
 |}&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
Please be aware that for an application to be considered by the board, '''you MUST have 5 recommendations'''.  &lt;br /&gt;
An incomplete application will not be considered for vote.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
{| style=&amp;quot;width:100%&amp;quot; border=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
 ! colspan=&amp;quot;8&amp;quot; align=&amp;quot;center&amp;quot; style=&amp;quot;background:#4058A0; color:white&amp;quot;|&amp;lt;font color=&amp;quot;white&amp;quot;&amp;gt;'''COMMITTEE RECOMMENDATIONS''' &lt;br /&gt;
 |- &lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:white; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;&lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:#7B8ABD; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;'''Who Recommends/Name''' &lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:#7B8ABD; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;'''Role in OWASP'''&lt;br /&gt;
 ! align=&amp;quot;center&amp;quot; style=&amp;quot;background:#7B8ABD; color:white&amp;quot;|&amp;lt;font color=&amp;quot;black&amp;quot;&amp;gt;'''Recommendation Content''' &lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''1'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''2'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''3'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''4'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |-&lt;br /&gt;
 | style=&amp;quot;width:3%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|'''5'''&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:20%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 | style=&amp;quot;width:57%; background:#cccccc&amp;quot; align=&amp;quot;center&amp;quot;|&lt;br /&gt;
 |}&lt;br /&gt;
----&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=133344</id>
		<title>Kuwait City</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Kuwait_City&amp;diff=133344"/>
				<updated>2012-07-23T20:25:07Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Kuwait الكويت|extra=مرحباً بكم بصفحة فرع الكويت لمنظمة أواسب!&lt;br /&gt;
&lt;br /&gt;
The chapter leader is [mailto:mohammed.aldoub@owasp.org Mohammed Aldoub],&lt;br /&gt;
&lt;br /&gt;
رئيس هذا الفرع هو  [mailto:mohammed.aldoub@owasp.org محمد الدوب,].|mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Kuwait|emailarchives=http://lists.owasp.org/pipermail/owasp-kuwait}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
نبشركم بإعادة افتتاح فرع أواسب بدولة الكويت برئيس جديد من تاريخ ٢٢ مايو ٢٠١٢. &lt;br /&gt;
OWASP Kuwait is pleased to announce a chapter restart with a new leader as of May 22, 2012!&lt;br /&gt;
&lt;br /&gt;
 '''Meeting Location'''&lt;br /&gt;
&lt;br /&gt;
Everyone is welcome to join us at our chapter meetings.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Middle East]]&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Asia/Pacific/Middle East]]&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=133343</id>
		<title>User talk:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User_talk:Mohammed_ALDOUB&amp;diff=133343"/>
				<updated>2012-07-23T20:07:42Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: /* Testing */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Welcome to ''OWASP''!'''&lt;br /&gt;
We hope you will contribute much and well.&lt;br /&gt;
You will probably want to read the [[Help:Contents|help pages]].&lt;br /&gt;
Again, welcome and have fun! [[User:KateHartmann|KateHartmann]] 11:26, 31 May 2012 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Testing ==&lt;br /&gt;
&lt;br /&gt;
Hello, I'm testing. If you see this, please say Hello World&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=User:Mohammed_ALDOUB&amp;diff=133342</id>
		<title>User:Mohammed ALDOUB</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=User:Mohammed_ALDOUB&amp;diff=133342"/>
				<updated>2012-07-23T20:00:29Z</updated>
		
		<summary type="html">&lt;p&gt;Mohammed ALDOUB: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Computer Engineer, Security Specialist and Shark Diver from Kuwait. &lt;br /&gt;
&lt;br /&gt;
If it's about computer security and secure development, I'm in.&lt;br /&gt;
&lt;br /&gt;
If it's about shark diving, I'm already in the water.&lt;br /&gt;
&lt;br /&gt;
OWASP Kuwait chapter leader, you can find me on twitter: [https://www.twitter.com/Voulnet @Voulnet]&lt;br /&gt;
&lt;br /&gt;
My interests are web app security, secure coding, privacy and smart cards.&lt;/div&gt;</summary>
		<author><name>Mohammed ALDOUB</name></author>	</entry>

	</feed>