Tampa BSides - Chef's Tour of Microsoft Security Adoption Framework (SAF)
Editor's Notes
\n
\n
\n
\n
\n
\n
\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
The most important feature for this discussion is that each Web site is a silo. The location metaphor works fine when what you want to do is confined to that silo. But what happens when you need information from multiple places to accomplish your task?\n
\n
\n
\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
complex event processing not unusual in the enterprise\njust developing on the more general Web\nidentity\nloosely coupled system\n
\n
KRL: \n- rule based\n- sophisticated event expressions\n- in cloud\n- API ready\n
No one’s ever surprised me with a GUI\nIndirection allows us to fix problems once\nLanguages are how programmers encapsulate problems and create abstractions\n
Abstraction layer\nMental model\n
\n
when you folloiw someone on twitter, you are creating a static query against the river of tweets\nwe’ve create a rule language, KRL, to work in this new model. \n
\n
\n
call out the abstract in this expression\n
we’ve already seen KRL rules employed in applications that increase customer satisfaction and make online interactions more convenient\n\n
patient doctor connections are more effective\n
parents create more play opportunities for their children\n
\n
\n
\n
\n
\n
Turn by turn directions are a good example of notifications providing value.\n