J.D. Meier's Blog : Guidance Explorer

Using Guidance Explorer from Outlook

J.D. Meier — Tue, 08 Jan 2008 20:15:06 GMT

It looks like Alik Levin has some helpful posts on using Guidance Explorer from Outlook:

Customize Guidance Explorer Inside Outlook 2007 – Find Tech Gold Nuggets Instantly - how to configure Outlook for easier searches using built-in functionality.
Consume patterns&practices Guidance Explorer Via RSS Using Outlook 2007 - how to set up RSS feeds inside Outlook to read GE’s content.

Alik is a long time patterns & practices user. He's intimately familiar with our security and performance bodies of guidance (BOG). He always surprises me with his ability to find every nugget among our vast collection (after all - we have a few thousand pages of patterns & practices security and performance guidance on MSDN.)

As an experienced security and performance consultant, Alik was already very efficient and effective with his customer delivery. I think he was the first person I saw start using Guidance Explorer to build customized guidance for customers. Now that he's taken GE to the next level with his Outlook integration, he's a security and performance machine!

How To Use Guidance Explorer to do a Security Code Inspection

J.D. Meier — Thu, 13 Dec 2007 16:52:47 GMT

One of the key experiences you get with Guidance Explorer (GE) is support for manual security inspections. We call them inspections versus reviews because we inspect against specific criteria. We supply you with a starter set of inspection questions, but you can tailor them or add your own.

Security Code Inspection
We use three distinct types of inspections: design, code and deployment. For this example, we'll use Guidance Explorer to do a security code inspection of an ASP.NET application.

Summary of Steps

Step 1. Create a new View.
Step 2. Add inspection questions to your view.
Step 3. Save your View to Word.

Step 1. Create a new View.
In this step, you add a new view to My Views. To do so, in GE, right-click, My Views, and add a new View. You can name your View whatever you like, but for this example, I'll name mine "Security Code Inspection."

Step 2. Add inspection questions to your view.
In this step, you add relevant security inspection questions. To do so, in GE, click the patterns & practices Library, next click Security, next click Security Engineering, next click Code Inspections. Expand the ASP.NET 2.0 set of security inspection questions.

For this example, drag and drop the questions from the following categories: Input and Data Validation, Forms Authentication, and SQL Injection. This will give you a nice focused set of questions to drive your inspection.

Step 3. Save your View to Word.
In this step, you save your View as a Word doc. To do so, right-click your view (e.g. "Security Code Inspection") and click Save Vew as .... Name your doc (e.g. "My Security Code Inspection.doc") and click Save.

You just built your own security code inspection set!

Extending and Exploring
There's a lot of exploring you can do and ways you can extend:

Design and Deployment Inspection: For example, you can try building a security design inspection set or a security deployment inspection set.
Code Examples. You can add code examples and link them to your inspection questions.
Agile Security Engineering. If you're doing Agile development, you can scope your security inspection to a finite set of categories for a specific set of stories within the current iteration.
Patterns. If you're a fan of patterns you can add pattern examples to your design inspection. At the end of the day, do what makes sense for you and your team to more effectively build software and meet your security objectives.

Share Your Stories
I'm sure you're bound to have stories. If you haven't done security code inspections before, you're in for a treat. Security Code Inspections are a proven practice. While the criteria and context may vary, the technique pretty much remains the same. Share your stories either in this post or send email to getool@microsoft.com.

My Related Posts

New Release: Guidance Explorer is Now on MSDN

How To Build Your Own Guide with Guidance Explorer

J.D. Meier — Mon, 05 Nov 2007 08:53:00 GMT

You can build your own guide using Guidance Explorer. Guidance Explorer is a front-end browser optimized for our patterns & practices guidance store. Here's some of the usage scenarios:

Build a guide of your favorite patterns & practices items.
Build a custom set of guidelines for your team.
Build a custom checklist for a security or performance inspection.
Build a customized guide for your customer.

Summary of Steps

Step 1. Create a new view.
Step 2. Add items to your view.
Step 3. Save your view as a Word doc.

Step 1. Create a new view.
To create a new view, right-click My Views and click New View. Name your view.

Step 2. Add items to your view.
For this example, select some items from the patterns & practices library node and drag and drop them into your view. Note that you can edit the items. Just double-click to bring up the item, then click Edit. Once you are happy with your changes then you can save to your read write libraries (such as My Library.) You can also create new items. For example, right-click My Library and click New Item. You can then add your new item to your View by dragging and dropping.

Step 3. Save your view as a Word doc.
Once you are happy with items in your view, right-click the view and save it as a Word doc. Note that you can also choose to save it as HTML.

Voila! You now have your very own, custom guide.

My Related Posts

Guidance Explorer: A Top Download on CodePlex

J.D. Meier — Mon, 15 Oct 2007 03:24:00 GMT

It was a nice surprise to see that our Guidance Explorer is among the top downloads on CodePlex.

New Video: How To - Personalize Team System Guidance with Guidance Explorer

J.D. Meier — Wed, 28 Mar 2007 09:20:00 GMT

If you are a hunter and gatherer of guidance, you'll want Guidance Explorer. Watch Video: How To - Personalize Team System Guidance with Guidance Explorer to see how you can use Guidance Explorer to build a custom collection of guidance from our Visual Studio Team System Guidance project. If you haven't used Guidance Explorer before, or it's been a while, you're in for a surprise. Seriously.

Guidance Explorer is a free tool to help you browse, find, organize, or even create your own guidance. When you launch Guidance Explorer, it synchronizes with our online store. For example, today's additions include a number of brand new Team System guidance items:

2 - Explained items
64 - FAQ items (these are actually our Questions and Answers)
43 - Mini How Tos (these are actually our Practices at a Glance)
6 - How Tos

My favorite Guidance Explorer features include:

Create collections of your favorite guidance (custom views)
Browse by checklists, code examples, how tos, guidelines (view by type)
Filter for just security, performance or Team System (Filter by technology, topic or category)
Share guidance among your teams (UNC share scenario)
Build a customized guide or whitepaper on the fly with exactly the parts you want (Save to Word, HTML or XML)
Create new guidance libraries and write your own personal guidance or checklists.

Keep in mind that Guidance Explorer is actually a diamond in the rough. It has its flaws, but it also has unique powers. For example, I could use Guidance Explorer to inform you of brand new, emerging security practices. I could also flag the top performance issues using the priority field. Imagine the alternative of hunting through a whitepaper or article, instead of organized collections and lists of actionable, guidance nuggets.

I know consultants that literally save themselves many hours per week by using Guidance Explorer as a personal knowledge base and for tailoring guidance for customers. I also know of customers using Guidance Explorer as a light-weight and effective way to share guidance among their development teams. It's actually the type of tool where customers surprise me what they use it for.

While Guidance Explorer has nearly 1100 guidance nuggets at last count (across security, performance and .NET 1.1. and 2.0), you can quickly shrink the haystacks to find the needle that you need (Ed and I call this our Shrinking Haystack pattern). You can also discover relationships among the guidance, because related items are linked. Don't take my word for it though, test drive it for yourself. Did I mention it's free? Oh yeah, I should also mention it comes with source, so shape it to your heart's content.

Go ahead and watch Video: How To - Personalize Team System Guidance with Guidance Explorer and then download Guidance Explorer. If you do use Guidance Explorer and you have a story you'd like to share, please leave a comment in this post.

Building a Custom Set of Guidance with Guidance Explorer

J.D. Meier — Tue, 20 Mar 2007 01:10:00 GMT

Today I was reminded of the powerful scenario for building a custom set of guidance on the fly using Guidance Explorer. One of the scenarios for Guidance Explorer that's probably not well known, is the ability to generate MS Word documents. You can also save to HTML or export to XML. The idea was that you could build a custom set of guidance by grabbing the guidance modules you wanted.

In my case, I needed to quickly create two documents -- a set of ASP.NET 2.0 security guidelines and a set of ASP.NET 2.0 security checklist items. To do this using Guidance Explorer, I took the following steps:

created a new view and named it ASP.NET 2.0 Security Guidelines
filtered the guidelines for ASP.NET 2.0 and Security
dragged the guidelines into my new view
clicked my view and then dragged the Category field over to the far left
sorted the Category field. This gave me a set of guidelines organized by key areas (authentication, authorization ... etc.)
right-clicked my view, chose Save View As ... and saved the doc to my desktop.

This gave me a single Word document of the ASP.NET 2.0 security guidelines with an index up front and the details in the doc. I repeated the steps to create a set of ASP.NET 2.0 security checklist items.

If necessary, I could have tailored the guidance before creating the document. Another feature that's not well known is that you can use Guidance Explorer as an authoring tool. You can quickly modify the content of guidance modules and then save to one of your read-write libraries.

Guidance 2.0

J.D. Meier — Sun, 04 Mar 2007 02:51:00 GMT

Imagine what a Guidance 2.0 world might be like ...

browse tag clouds of reusable "architecture nuggets"
subscribe to "guidance feeds" that give you the latest practices and recommendations
share your "guidance" playlists with friends (share your favorite collections of how tos, guidelines, checklists)
build guidance mashups from your favorite trusted sources of information
rate the guidance and rate the raters (think Amazon or EBay)
browse a federation of guidance Wikis in your company and in the community

I think next-gen guidance is about bringing together a lot of key concepts:

context-precision (using context to organize information)
personalization (create your own views, tailor it for your needs, ... etc.)
community type ratings (expose the thinking and rate the raters for the guidance)
guidance types (evolvable schemas for guidance types, such as how tos, guidelines, checklists, patterns ...)
Folksonomy over taxonomy

A lot of today's guidance lives in blogs. Part of the problem (and beauty) of blogs is that every end node is a blob of information. What if there were RSS end nodes that contained "collections" or "lists" of how tos, guidelines, patterns ... etc.? From a very practical standpoint, I would love to subscribe to the latest MS (or any company) recommendations and view those in a type of my choice (patterns, guidelines, how tos ... etc.) The mashupability is endless.

Those are the ideas that drove and shaped Guidance Explorer. Guidance Explorer was just one small step towards a world of more effective and efficient guidance.

24 ASP.NET 2.0 Security FAQs Added to Guidance Explorer

J.D. Meier — Wed, 17 Jan 2007 21:39:00 GMT

We published 24 ASP.NET 2.0 Security FAQs now in Guidance Explorer. You'll find them under the patterns & practices library node. We pushed the FAQs into Guidance Explorer because one of our consultants in the field, Alik, is busy building out a customer's security knowledge base using Guidance Explorer.

Don't let the FAQ name fool you. FAQ can imply high-level or introductory. These FAQs actually reflect some deeper issues. In retrospect, we should have named this class of guidance modules "Questions and Answers."

Each FAQ takes a question and answer format, where we summarize the solution and then point to more information.

Enjoy!

Guidance Explorer as Your Personal Guidance Store

J.D. Meier — Mon, 15 Jan 2007 21:28:00 GMT

Although Guidance Explorer (GE for short) was designed to showcase patterns & practices guidance, you can use it to create your own personal knowledge base. It's a simple authoring environment, much like an offline blog. The usage scenario is you create and store guidance items in "My Library".

While using GE for day to day use, I noticed a simple but important user experience issue. I think we should have optimized around creating free-form notes, that you could later turn into more structured guidance modules. There's too much friction to go right to guidance, and in practice, you start with some notes, then refine to more structure.

To optimize around creating fre-form notes in GE, I think the New Item menu that you get when you right-click the MyLibrary node, should have been:
1. Note - This would be a simple scratch pad so you could store unstructured notes of information.
2. Guidance Module - This menu option would list the current module types (i.e. Checklist Item, Code Example, … etc.)

We actually did include the "Technote" type for this scenario. A "Technote" is an unstructured note that you can tag with meta-data to help sort and organize in your library. The problem is that this is not obvious and gets lost among the other structured guidance types in the list.

The benefit of 20/20 hind-sight strikes again!

On a good note, I have been getting emails from various customers that are using Guidance Explorer and they like the fact they get something of a structured Wiki experience, but with a lot more capability around sorting and viewing chunks of guidance. They also like the fact that you get templates for key types (so when five folks create a guideline, all the guidelines have the same basic structure.) I'll post soon about some of the key learnings that can help reshape creating, managing and sharing your personal, team, and community knowledge in today's landscape.

844 Guidance Items in Guidance Explorer

J.D. Meier — Tue, 09 Jan 2007 07:53:00 GMT

It's not 9 new guidelines, it's actually 70. It looks like my Guidance Explorer wasn't done synching when I wrote my previous post.

Prashant sent me a quick note. Here is the complete status for Dec and Jan

Dec – 33 Guidelines items (.NET 2.0)
Jan – 37 Guidelines items (ADO.NET 2.0)

Total Items – 844
Total Guidelines Items – 547

9 New Perf Guidelines in Guidance Explorer

J.D. Meier — Mon, 08 Jan 2007 23:55:00 GMT

You should see 9 new performance guidelines in Guidance Explorer (GE). Well, not entirely new, but refactored and cleaned up. Prashant Bansode (from our original Improving .NET Performance guide team) was busy while I was out of office for the holidays. What you'll notice is that many of the guidelines are missing problem and solution examples. Job #1 is first putting the guidance into this form. Our new schema for guidelines is more elaborate than the original guidance, which means we'll have information holes. Fleshing out the missing information would be job next.

BTW - if you're using Guidance Explorer and have an interesting story on how you've used it, please share it with us at getool@microsoft.com.

From Guides to Guidance Modules

J.D. Meier — Sun, 07 Jan 2007 04:59:00 GMT

Have you noticed the transition from guides to guidance modules over time? My first few guidance projects were actually guides:

While the chapters in the guides were modular, the overall outcome was an end-to-end guide. On the upside, there was a lot of cohesion among the chapters. On the downside, the guides were overwhelming for many customers who just wanted bits and pieces of the information. That's the challenge of making a full guide available in html, pdf and print.

Examples of Guidance Modules
.NET 2.0 Security Guidance was the first project to use "Guidance Modules". Guidance Modules are effectively modular types of guidance:

Cheat Sheets (Cheat Sheet example)
Checklists (Checklists example)
Explained (Explained example)
Guidelines (Guidelines example)
How Tos (How To example)
Practices (Practices example)

Benefits of Guidance Modules
The benefits of modules include:

"right-size" the solution to the problem
easier to author and test the guidance (templates and test cases)
easier to consume (you can grab just the guidance you need)
release as we go vs. wait until the end
you can build guides and books from the modules (strong building blocks for guides)

The Chunking Has Just Begun
While the initial chunking of guidance has certainly helped, there's more to go. Customers have asked for even smaller chunks. For example, rather than have all the guidelines in a single module, chunk each guideline into its own page.

Dealing with Chunks
Chunking up the guidance creates new challenges. How do you find, gather and organize the right set of modules for your scenario? This is a good problem to have. Assuming there's guidance modules that have great community around them and they're prescriptive in nature (it prescribes vs. describes solutions), then the next step is to improve how you can leverage the modular information. That's where Guidance Explorer comes in. It was an experiment to explore new ways of creating, finding, and using guidance modules. We learned a great deal about user experience, which I'll share in a future post.

238 New Items in Guidance Explorer

J.D. Meier — Mon, 20 Nov 2006 23:52:00 GMT

Today we published 238 new guidance items in Guidance Explorer. If you use the offline client, it should automatically synchronize to our online store.

We're in the process of performing a guidance sweep. The approach to the sweep is twofold:
1. Make existing guidance available in Guidance Explorer.
2. Identify user experience issues with the information models and tool design.

Benefits in GE
Making existing guidance available in Guidance Explorer involves re-factoring existing security guidance and performance guidance. The benefits of having the guidance available in Guidance Explorer include:

you can view across topics (for example, you can see across the security and the performance guidance)
you can filter down to exactly the guidance items you need for a given scenario or task
you can build multiple custom views based on how you need to use the guidance
you can build guides on the fly (you can save a view as a Word doc or HTML files for example)
you can tailor the guidance to your scenario (e.g. save an item into your library in GE and edit the guidance to your liking)
you can supplement the guidance for your scenario (because GE is also an authoring environment, you can write your own guidance)

How We Improve Our Guidance
An underlying strategy in GE was to help support users quickly hunt and gather relevant items rather than try and guess your context and what you need. In other words, it's a tool to help smart people versus a smart tool that might get in your way. This was actually an important decision because we had to pick a problem we knew we could help directly solve and add value.

The feedback from customers on existing guidance was that it was great stuff, but there were 3 key problems:
1. it's a copy+paste exercise to grab just the guidance you need
2. it's not atomic enough (monoliths over bite-sized chunks)
3. many of the items, while they read well, were not actionable enough

That's why we took the following measures on our guidance:

split the guidelines and checklists into individual items (we chunked the guidance into units of action)
we cleaned up our templates for the various guidance types (we gave the chunked items a common look and feel)
made the schema explicitly include answers to "why" and "how", as well as include problem examples and solution examples (we made the chunks more actionable and verifiable)

As we port existing guidance to our updated schemas, we often find guidance items lacking key information such as why or how, or example code.

Guidance Explorer in Practice
What's been great so far is that some folks in the field have let me know how they've been using it for customer engagments. Apparently the ability to customize guidance has resonated very well. One consultant in particular has used Guidance Explorer for several engagements to save time and effort. He uses GE as a general purpose rules and guidelines store. He's also tailored guidelines and checklists for different audience levels (executive, development leads, architects, developers, PMs) and for different activities (design reviews, code reviews, and deployment reviews).

A few customers have let me know they are using the UNC share scenario to create guidance libraries for their team development. They told me they like the idea that it is like a simple typed-wiki that you can act on. The fact that they can create views and print out docs from the library has been the main appeal.

The other benefit that more customers are appreciating is the templates for guidelines and checklists. They like the fact that it starts to simplify authoring as well as sharing prescriptive guidance. For anybody who has authored guidelines or checklists, they know that it's challenging to write actionable guidance that can be reused. What we're sharing in Guidance Explorer is the benefit of experience and lessons learned over the years of producing resuable guidance for various audiences.

R&D Project
As a reminder and to keep things in perspective, Guidance Explorer is an R&D project. While there are immediately tangible benefits, the real focus is on the learnings around user experience so that patterns & practices can improve it's ability to author and share guidance, and to make progress on helping debottleneck the creation of prescritive guidance for the software industry.

Feedback
You can send feedback on GE directly to the team at getool@microsoft.com

Guidance Explorer Beta 2 Release

J.D. Meier — Tue, 03 Oct 2006 01:40:00 GMT

We released Guidance Explorer Beta 2 on CodePlex. Guidance Explorer is a patterns & practices R&D project to improve finding, sharing and creating prescriptive guidance. Guidance Explorer features modular, actionable guidance in the form of checklists, guidelines, how tos, patterns … etc.

What's New with This Release

Guidance Explorer now checks for updated guidance against an online guidance store.
Source code is available on CodePlex so you can shape or extend Guidance Explorer for your scenario.
Guidance Explorer Web Edition is available for quick browsing of the online guidance store.

Learn More

View the screenshots of Guidance Explorer for a quick look at some of the basic features.
View the Overview slides for a short walkthrough of Guidance Explorer.

Resources

Feedback
Send your feedback to getool@microsoft.com.

Test Our patterns and practices Guidance Explorer

J.D. Meier — Wed, 24 May 2006 00:15:00 GMT

I've been relatively quiet these past few weeks, getting ready to release our patterns & practices Guidance Explorer. Guidance Explorer is a new, experimental tool from the patterns & practices team that radically changes the way you consume guidance as well as the way we create it. If you’ve felt overwhelmed looking across multiple sources for good security or performance guidance then Guidance Explorer is the tool for you. You can use one tool to access a comprehensive, up to date, collection of modular guidance that will help you with your tough development tasks and design decisions. Guidance Explorer will allow you to create and distribute a set of standard best-practices that your team can adhere to for performance and security. The project includes the tool, Guidance Explorer, and a library of guidance for developers, Guidance Library. The Guidance Library will be updated weekly, ensuring you always have the most up to date information.

What's In It For You

If you build software with the .NET Framework, use Guidance Explorer to find the "building codes" for the .NET technologies, in terms of security and performance. They are complimentary to FX Cop rules.
If you want to set development standards and best practices for your team, use Guidance Explorer views to build and then distribute your team’s standard rule-set.
If you author guidance for development teams, use Guidance Explorer to create guidance for your teams in a more efficient and effective way by leveraging our templates, information models, key concepts, and tooling support.

What is Guidance Explorer
Guidance Explorer is a client-side tool that lets you find, filter, and sort guidance. You can organize custom guidance collections into persistent views and share these views with others. You can also save these custom views of the guidance as indexed Word or HTML documents. You can browse guidance by source, such as the patterns & practices team. You can also browse by topic, such as security or performance, or by technology, such as ASP.NET 1.1 or ASP.NET 2.0. Within a given topic or technology, you can then browse guidance within more fine-grained categories. For example, within security, you can browse by input/data validation, authentication, authorization .. etc.

Guidance Explorer was designed to simplify the creation and distribution of custom guidance. To author guidance, Guidance Explorer, includes a simple editor that uses templates for guidance. Each template includes a schema and test cases. For example, each guideline item should include what to do, why, how, a problem example, and solution example, as well as related items and where to go for more information. We created these templates by analyzing what's working and not working from our several thousands of pages of guidance over the past several years, around security and performance.

What is Guidance Library
Guidance Library is the collection of knowledge that is viewable by Guidance Explorer. It's organized by types, such as guidelines and checklists. Each type has a specific schema and test cases against that schema to help enforce quality. The library is also organized by topics, such as security and performance. The library is extensible by design so that we can add new types and new topics that prove to be useful.

Not every type of guidance goes into the guidance library. For example, you don't use it to find monolithic guides or PDFs. The most important criteria for the modules in the library is that they are atomic units of action. They can directly be tested for relevancy. They can also be tested for the results they produce and how repeatable those results are.

How To Get Started

Join the Guidance Explorer project
Download Guidance Explorer
Watch the video tutorials

The key to getting started is getting the tool up and running so you can play with it, and watching the short videos (1-2 minute long) to learn the main features and usage scenarios.

Your First Experiment with Guidance Explorer
For your first test with Guidance Explorer, try creating a Word doc that has just the guidelines you want.

To run your first experiment:

Create a custom view of the guidance
Save the view fo the guidance as a Word doc

How To Get Involved

Join the CodeGallery workspace. To join the workspace, sign up at the Guidance Explorer Home on Codegallery
Subscribe to the RSS feeds. To subscribe to the feeds, use the RSS buttons in each section of Guidance Explorer Home on Codegallery
Participate in the newsgroups. To participate in the newsgroups, use the Guidance Explorer Message Boards on Codegallery
Provide feedback on the alias. To do so, send email to GETOOL at Microsoft.com.

What's Next
These are some of the ideas we'd like to implement:

VS.NET integration
refactoring additional guidance (e.g. existing patterns & practices guidance such as the data access, exception management, and caching guidance)
New guidance types (such as "test cases", "code examples", "project patterns", "whiteboard solutions")
New topics (such as reliability, manageability, … etc.)
integrating bodies of guidance and ecosystems (such as integration with product documentation)

I also hope to create a model for "Guidance Feeds", where you can subscribe to relevant guidance, as well as integrate many of the emerging social software concepts, such as allowing the network/community to rate the guidance, rate the raters and contributors, and create community-driven, shareable custom views.

About Our Team
Our core team consists of:

Prashant Bansode. Prashant was a core member of my Whidbey Security Guidance Project, so he's very seasoned. I chose him specifically because of his unmatched ability to execute, and because he is one of the best customer champions I know. What surprised me about Prashant is his ability to not only manage his own work, but help guide others, and he really gets how to deliver incremental value.
Diego Gonzalez. Diego is a coding machine. He's also capable of bridging dreams and reality with working models. Usually, by the time you've finished your sentence on what you'd like to see, Diego's already implementing it.
Ed Jezierski. Ed's simply brilliant. I've never seen a more impressive mix of people focus and technical expertise. If you can dream it up, Ed can make it happen. If you can't dream it up, Ed can dream it up for you. Just insert a random wish and Ed can turn it into a working prototype, and incredible slideware to match. Ed brings to the table a ton of social software concepts and ideas around taking guidance to the next level. I've worked with Ed for many years, but it's been a while since we've partnered up on the same project. I look forward to many brainstorms, whiteboard sessions, and off the deep end conversations over lunch.
Ariel Neisen. Ariel is a developer on the team. Ariel works for Lagash with Diego and has been Diego's coding partner.
Mike Reinstein. Mike works for Security Innovation. He's a Web application security expert. He not only brings security development and design experience, but strong technical writing skills that have contributed to exceptional content.
Paul Saitta. Paul is previously a member of IO Active, now working for Security Innovation. He's an expert in Web applications and white-box security audits. He's been able to distill thousands of hours of customer audits into prescriptive guidance that illuminates common mistakes in the real world.
Jason Taylor. I first met Jason during my Whidbey Security Guidance Project. He impressed me with his ability to think on his feet, execute at a rate faster than most people can ever imagine, and his ability to distill and document expertise at a level few individuals can go. Jason has 7 years Microsoft experience under his belt, and was one of Microsoft's first test-architects. Now he's a V.P. for Security Innovation's security consulting group. Aside from bringing a wealth of security experience to the table, Jason has a lot of ideas around how to improve guidance for customers in very practical ways.

Key Links