Dear All, We're thrilled to announce the schedule of the first and second series of DFIR Stream.

On behalf of the Association of Cyber Forensics and Threat Investigators (ACFTI), I am pleased to

2 nd International Workshop on Cyber Forensics and Threat Investigations Challenges October 10-11,

The Association of Cyber Forensics and Threat Investigators (ACFTI) is an ambitious, non-profit

Apologies if you receive multiple copies of this initial call for papers. Please forward this initial

[Apologies for multiple cross-posting] 1st International Workshop on Cyber Forensics and Advanced

Hi All – just wanted to update everyone on our Saturday meeting. Below are the meeting notes. 1. Put

Hi all, I would be delayed in joining the call today. Please continue with the call and I will join

Hey all, I may not make it back in time to fire up Skype and be on the call, but did want to

Hey, I've compiled a list of resources on threat modeling based on information available on the

Upender, As Jack says, applicable "Security Best Practices and "common vulnerabilities

Quick and dirty software centric mind map madness.... Tony UcedaVelez Atlanta Chapter Leader

Sent a rescheduling email to you to see if we could push the day back. I am at a client site till

cheers, Rakkhi ---------- Forwarded message ---------- From: Rakkhi Samarasekera <rakkhi@rakkhis.

Guys - I want to remind everyone that John has shared Threat Modeling Glossary with the group. You

Spelling: that should have been prioritization. cheers, Rakkhi On 10 May 2011 17:25, Rakkhi

I've shared Threat modelling methodology Click to open: Threat modelling methodology Google Docs

I've shared OWASP_Threat_Modeling_Project.ppt Click to open: OWASP_Threat_Modeling_Project.ppt

-- Reef Dsouza Product Manager MyAppSecurity Inc. http://www.linkedin.com/in/reefdsouza http://www.

Tues at that time works best for me. Tony On Wed, May 4, 2011 at 12:11 AM, Venkatesh Jagannathan <

Looks good. Let's roll on. Sent from my mobile device. Please excuse any typos. On May 2, 2011,

On the point related to technical scope, I think we agreed in an earlier thread that anything client-

All, Quick clarification: some wonder about how/why I sourced what I did when defining terms. I used

I've shared Threat modelling resources Click to open: Threat modelling resources Google Docs

I've shared OWASP Threat Modeling Click to open: OWASP Threat Modeling Google Docs makes it easy