With cloud and SaaS gaining increased adoption by Enterprises, the next big challenge is how to achieve real time integration between the cloud applications and the on-premise applications. Follow my blog at http://www.kannan-subbiah.com/
The document provides an overview of enterprise application integration (EAI) and the Zachman Framework for enterprise architecture. It discusses the evolution of enterprise applications from data processing to business processes. It also summarizes the Zachman Framework, which provides a standard way to describe and define an enterprise based on six fundamental questions (what, how, where, who, when, why) and perspectives (contextual, conceptual, logical, physical).
This document provides an overview of enterprise application integration (EAI), including definitions, objectives, components, advantages, and examples. EAI involves integrating independently developed applications that may use different technologies. It has become a priority for many companies and is expected to be a $50 billion market by 2001. Key components of EAI solutions include business rule/logic modules, data acquisition interfaces/adapters, development tools, message brokers, and system control/management tools. Examples demonstrate how EAI can integrate e-commerce sites with legacy systems to share order and customer data.
Enterprise Application Integration TechnologiesPeter R. Egli
Overview of Enterprise Application Integration Technologies.
Enterprise Application Integration, or EAI in short, aims at integrating different applications into an IT application landscape. Traditionally, EAI was understood as using the same communication infrastructure by all applications without service-orientation in mind. This meant that the benefits of a shared infrastructure were limited while driving up costs through additional integration platforms.
Service Oriented Architectures (SOA) brought a new paradigm by decomposing applications into reusable and shareable services. Service orientation requires careful design of services. A hierarchic scheme of services may help to define a suitable service decomposition.
While SOA is technically based on big web service technologies, namely SOAP, WSDL and BPEL, WOA or Web Oriented Architecture stands for the lightweight service paradigm. WOA makes use of REST-based technologies like JSON and HTTP.
In many cases, an Enterprise Service Bus (ESB) is used as an infrastructure element to achieve the technical integration of the services. The ESB core functions like message routing, filtering and transformation provide the mediation services required to integrate heterogeneous application landscapes.
The document discusses Oracle Application Integration Architecture (AIA) for Communications and its benefits for integrating Oracle Communications applications. It describes how AIA uses pre-built integrations called Process Integration Packs (PIPs) to provide standardized, reusable integrations between applications like CRM, billing, order management and inventory. The presentation evaluates claims about AIA and concludes it is worthwhile for integrating Oracle Communications applications and is a strategic long-term solution.
Employing Enterprise Application Integration (EAI)elliando dias
This document discusses employing enterprise application integration (EAI) to achieve a zero-latency enterprise (ZLE). It describes what EAI is and what is driving its momentum, including the explosion of the internet and demand for integration. Current integration problems are outlined. The document discusses the types of integration and implementation architectures for EAI. It also compares EAI to traditional middleware and examines emerging standards like XML, SOAP and UDDI that are important for EAI. Key ingredients for a successful EAI solution and benefits of integration are presented.
Presentation from the developer track at I Love APIs London 2016 featuring Andrew Liles, DigitasLBi, George Taylor, DigitasLBi and Timothy Yip, DigitasLBi.
Managing 100s of Partner API integrations are difficult, because it requires careful management of both business relationships and technology, but what happens if you need to scale 1000s of integrations all across the globe?
DigitasLBi present the technology and governance techniques used to manage the thousands of apps and the thousands of backend systems. This presentation covers:
1. How to handle 1000s of integration configurations
2. How to govern the continual evolution of 10 APIs, publicising contracts such that automated tools can enforce the contracts
3. Emulating integrations during development
Presented by: Hector Martinez, Staff Solution Consultant, TIBCO Spotfire
TIBCO Spotfire and Teradata: First to Insight, First to Action; Warehousing, Analytics and Visualizations for the High Tech Industry Conference
July 22, 2013 The Four Seasons Hotel Palo Alto, CA
Arun Reddy, Technical Director at Raastech, gave a presentation on Oracle Fusion Middleware infrastructure best practices at Schoolcraft College. The presentation covered common best practices for installations, patching, administration, deployments, and security of Oracle Fusion Middleware. It provided guidance on operating system tuning, separation of binaries and configurations, deployments, backups, security configurations, and administration activities. The goal was to help administrators reduce maintenance and have a more stable and highly available Oracle Fusion Middleware infrastructure.
The document provides an overview of enterprise application integration (EAI) and the Zachman Framework for enterprise architecture. It discusses the evolution of enterprise applications from data processing to business processes. It also summarizes the Zachman Framework, which provides a standard way to describe and define an enterprise based on six fundamental questions (what, how, where, who, when, why) and perspectives (contextual, conceptual, logical, physical).
This document provides an overview of enterprise application integration (EAI), including definitions, objectives, components, advantages, and examples. EAI involves integrating independently developed applications that may use different technologies. It has become a priority for many companies and is expected to be a $50 billion market by 2001. Key components of EAI solutions include business rule/logic modules, data acquisition interfaces/adapters, development tools, message brokers, and system control/management tools. Examples demonstrate how EAI can integrate e-commerce sites with legacy systems to share order and customer data.
Enterprise Application Integration TechnologiesPeter R. Egli
Overview of Enterprise Application Integration Technologies.
Enterprise Application Integration, or EAI in short, aims at integrating different applications into an IT application landscape. Traditionally, EAI was understood as using the same communication infrastructure by all applications without service-orientation in mind. This meant that the benefits of a shared infrastructure were limited while driving up costs through additional integration platforms.
Service Oriented Architectures (SOA) brought a new paradigm by decomposing applications into reusable and shareable services. Service orientation requires careful design of services. A hierarchic scheme of services may help to define a suitable service decomposition.
While SOA is technically based on big web service technologies, namely SOAP, WSDL and BPEL, WOA or Web Oriented Architecture stands for the lightweight service paradigm. WOA makes use of REST-based technologies like JSON and HTTP.
In many cases, an Enterprise Service Bus (ESB) is used as an infrastructure element to achieve the technical integration of the services. The ESB core functions like message routing, filtering and transformation provide the mediation services required to integrate heterogeneous application landscapes.
The document discusses Oracle Application Integration Architecture (AIA) for Communications and its benefits for integrating Oracle Communications applications. It describes how AIA uses pre-built integrations called Process Integration Packs (PIPs) to provide standardized, reusable integrations between applications like CRM, billing, order management and inventory. The presentation evaluates claims about AIA and concludes it is worthwhile for integrating Oracle Communications applications and is a strategic long-term solution.
Employing Enterprise Application Integration (EAI)elliando dias
This document discusses employing enterprise application integration (EAI) to achieve a zero-latency enterprise (ZLE). It describes what EAI is and what is driving its momentum, including the explosion of the internet and demand for integration. Current integration problems are outlined. The document discusses the types of integration and implementation architectures for EAI. It also compares EAI to traditional middleware and examines emerging standards like XML, SOAP and UDDI that are important for EAI. Key ingredients for a successful EAI solution and benefits of integration are presented.
Presentation from the developer track at I Love APIs London 2016 featuring Andrew Liles, DigitasLBi, George Taylor, DigitasLBi and Timothy Yip, DigitasLBi.
Managing 100s of Partner API integrations are difficult, because it requires careful management of both business relationships and technology, but what happens if you need to scale 1000s of integrations all across the globe?
DigitasLBi present the technology and governance techniques used to manage the thousands of apps and the thousands of backend systems. This presentation covers:
1. How to handle 1000s of integration configurations
2. How to govern the continual evolution of 10 APIs, publicising contracts such that automated tools can enforce the contracts
3. Emulating integrations during development
Presented by: Hector Martinez, Staff Solution Consultant, TIBCO Spotfire
TIBCO Spotfire and Teradata: First to Insight, First to Action; Warehousing, Analytics and Visualizations for the High Tech Industry Conference
July 22, 2013 The Four Seasons Hotel Palo Alto, CA
Arun Reddy, Technical Director at Raastech, gave a presentation on Oracle Fusion Middleware infrastructure best practices at Schoolcraft College. The presentation covered common best practices for installations, patching, administration, deployments, and security of Oracle Fusion Middleware. It provided guidance on operating system tuning, separation of binaries and configurations, deployments, backups, security configurations, and administration activities. The goal was to help administrators reduce maintenance and have a more stable and highly available Oracle Fusion Middleware infrastructure.
Integration patterns and practices for cloud and mobile computingSHAKIL AKHTAR
This document discusses integration patterns and practices for cloud and mobile computing. It begins with an introduction to the presenter and an overview of the topics to be covered, including enterprise integration patterns (EIPs), integration best practices for connected systems, patterns for cloud and mobile computing, and use cases. Various integration styles, patterns for cloud-to-cloud and mobile integration are described. The document provides examples of real-time, queue-based and event-based integration approaches for enterprise mobile applications.
The document discusses REST APIs and design patterns. It provides examples of APIs that do and do not strictly follow REST principles, but can still be successful. It emphasizes that good API design considers how the API will actually be used and iteratively incorporates feedback. APIs need not follow all REST principles to be effective if they meet the real needs of their users and are well designed.
Guide to Application Performance: Planning to Continued OptimizationMuleSoft
Supporting everything from mobile apps with thousands of concurrent users to global deployments processing millions of requests daily, Anypoint Platform has been put to test. In this session, MuleSoft experts will talk through case studies from our most demanding deployments and provide a best practice approach to designing and tuning applications for optimal performance.
Unilever: Driving Integration Speed and Agility - Frank Brandes, Director of ...MuleSoft
Owning over 400 brands in 190 countries, Unilever is one of the largest CPG companies in the world. The existing integration landscape includes over 12,000 interfaces, connecting over 1,600 endpoints and processing on average 1.6 million transactions per day. The current Center of Excellence (CoE)model has been successful at supporting the core business in a cost efficient and resilient way, however with the increase of disruptive technologies such as Cloud and Mobile a new capability was required to support the business requirements and increase agility. Mulesoft have partnered with Unilever to establish an in-house Adaptive Integration capability, operating a DevOps framework focused on driving self-service and API connectivity as part of a Centre for Enablement model. In this presentation Unilever will explain the approach they have taken, challenges and opportunities that have arisen as part of the transformation.
The Future of B2B: Applying API-Led Connectivity to B2B/EDI - Eric Rempel, CI...MuleSoft
B2B/EDI is often associated with staid, legacy technologies. Yet the business processes B2B/EDI supports are often those under most pressure to become more agile and flexible. Hear how industry leaders are meeting this challenge through applying API-led connectivity to B2B/EDI.
API Description Languages: Which is the Right One for Me?Akana
SOA Software Director of API Strategy, Laura Heritage, discusses new ways to describe and document APIs have emerged such as Swagger, RAML, API Blueprint and others, each taking a slightly different approach. Please join us in this webinar to hear how these description languages differ and how to choose right one for your API.
This document discusses enterprise application integration (EAI), which seeks to provide efficient, reliable data exchange between multiple enterprise applications. EAI involves integrating various types, including information portals, data replication, shared business functions, service-oriented architecture, and distributed business processes. The main challenges with integration are that networks are unreliable and slow, and any two applications are different. Common integration approaches include file transfer, shared databases, remote procedure invocation, and messaging. Messaging in particular allows for high-speed, asynchronous, and reliable integration through send-and-forget and store-and-forward communication.
Microservices is one of the hottest technology trends this year. In this presentation you'll see what microservices mean for your business, and learn about microservices best practices and implementation using Anypoint Platform.
This presentation will include:
-What is the microservices approach and how to achieve business agility with it
-How continuous delivery/continuous integration principles tie in with microservices
-How to implement microservices using Anypoint Platform
This presentation discusses Mule ESB and how to simplify integration. It briefly mentions a brief history of integration, information silos, SOA. It also highlights several integration patterns.
The document summarizes what Google learned over 10+ years of building cloud infrastructure and services, including embracing assumptions of running everything in the cloud, redundancy across data centers, and eventual consistency. It discusses trends that emerged like containers, microservices, serverless computing, and security becoming even more important. The key lessons are to not compromise on developer productivity, be open to alternatives but cautious of blindly following trends, and that security can never be too careful.
Google has invested $27 billion in data centers worldwide since 2014 to build the world's fastest and most powerful cloud infrastructure. In 2016, Google Cloud Platform experienced 36% year-over-year growth in bookings, a 50% increase in net customer count, and over 90 new features shipped. Google processes over 1 billion API calls per day and saw 58% year-over-year growth in Black Friday traffic.
Microservices - Death of the Enterprise Service Bus (ESB)? (Update 2016)Kai Wähner
Microservices are the next step after SOA: Services implement a limited set of functions. Services are developed, deployed and scaled independently.
Continuous Integration and Continuous Delivery control deployments. This way you get shorter time to results and increased flexibility. Microservices have to be independent regarding build, deployment, data management and business domains. A solid Microservices design requires single responsibility, loose coupling and a decentralized architecture. A Microservice can to be closed or open to partners and public via APIs. This session discusses the requirements, best practices and challenges for creating a good Microservices architecture, and if this spells the end of the Enterprise Service Bus (ESB). A live demo will show how middleware and Microservices complement each other using containers, continuous integration, REST services, and open source frameworks such as Cloud Foundry.
A live demo showed a "Microservices Middleware Architecture" using Cloud Integration (with Cloud Foundry PaaS), Integration and Services (with TIBCO BusinessWorks Container Edition), API Management / Open API (with Mashery) amd Log Management / IT Operations Analytics (ITOA, with Papertrail and LogLogic / Unity).
Thinking about incorporating digital trends like AR/VR, IoT, and cognitive analytics into your business? What should you think about? How can you derive enterprise value from these trends? Join Bill Briggs, the CTO of Deloitte Consulting, LLP, and Ross Mason, the founder and VP of Product Strategy at MuleSoft, who will talk about how organizations are using these trends and what you need to know to get started.
Microservices Done Right: Key Ingredients for Microservices SuccessApigee | Google Cloud
This document discusses microservices and keys to microservices success. It defines microservices as independently deployable services that work together. Microservices allow for agility, reuse, and productivity. The document outlines how enterprises are adopting microservices with containers, registries, auto-scaling and blue/green deployments. It emphasizes that REST APIs are a key ingredient for microservices success by enabling consumption and shielding consumers from complexity. The document also notes that microservices will fail without API management for issues like API sprawl, security threats and lack of visibility. It positions Apigee as providing the API layer and management capabilities needed for successful microservices.
Each and every business is unique. From healthcare to retail, manufacturing or finance — no two businesses
operate the same way. That’s why the Microsoft Cloud can be tailored to meet the needs of any enterprise.
It’s the cloud that helps drive unparalleled productivity. The cloud that turns massive streams of data into
actionable insight. The cloud that scales rapidly t o meet the growing demands of your business. And the
cloud that transforms a mobile workforce into a connected team. This is the cloud that’s built for your business.
The document describes design patterns for enterprise application integration (EAI). It discusses patterns related to service oriented architecture, notification, composition, testing, and optimization. Specific patterns covered include interoperability, service directory, event monitor, observer, publish/subscribe, and messaging bridge. The document provides goals, solutions, diagrams, and hints for each pattern to help with common integration problems.
Amazon began in 1994 as an online bookstore and has since grown to become the largest online retailer in America. It operates 7 websites globally and offers over 20 million products. There are four primary drivers of Amazon's growth: product focus, customer focus, technology focus, and distribution focus. Amazon deals with fluctuating demand through a multi-tier inventory model that aggregates inventory and purchases low demand items in response to customer orders to reduce costs.
This document provides a high-level overview of key components in telecom OSS/BSS systems. It discusses general concepts like numbering plans and call scenarios. It then summarizes the main components, including data collection, mediation, billing, SS7 monitoring, revenue assurance, and fulfillment/provisioning. The document provides brief explanations of the purpose and processes within each component.
Implementing an Effective Third-party & Vendor Risk Management ProgramKannan Subbiah
This document discusses implementing an effective third-party and vendor risk management program. It covers selecting a framework, the relationship lifecycle which includes strategy, due diligence, contracting, ongoing monitoring and re-evaluation. Key focus areas are scope, segmentation, due diligence, control systems, risk assessments, governance, organization, policy, tools and data. Recommendations include building a cross-functional team, being comprehensive without complexity, staying agile with risk-based intelligence, and complementing decision making with risk-based intelligence. The document also discusses compliance challenges, recovering from breach, next steps of integrating the approach and leveraging automation.
Developing & Deploying Effective Data Governance FrameworkKannan Subbiah
This is the slide deck presented at the Customer Privacy and Data Protection India Summit 2019 held in Mumbai, India. The specific topics touched upon are the guiding principles, Aligning with Data Architecture, Data Quality & Compliance.
Cyber fraud and Security - What risks does family office's face intoday's wo...Kannan Subbiah
Presented at the Private Wealth Management Summit 2017 held at Mumbai, India.
Security has to be considered as the foundation on which one can build a business. Gone are the days when we can build a perimeter, sit back and feel secure. In today’s digital environment we partner with others, we outsource, we have alliances, we let our customers into our systems and as we extend our networks.
In the digital economy, effective cyber security can mean the difference between a business’s success and its failure.
Integration patterns and practices for cloud and mobile computingSHAKIL AKHTAR
This document discusses integration patterns and practices for cloud and mobile computing. It begins with an introduction to the presenter and an overview of the topics to be covered, including enterprise integration patterns (EIPs), integration best practices for connected systems, patterns for cloud and mobile computing, and use cases. Various integration styles, patterns for cloud-to-cloud and mobile integration are described. The document provides examples of real-time, queue-based and event-based integration approaches for enterprise mobile applications.
The document discusses REST APIs and design patterns. It provides examples of APIs that do and do not strictly follow REST principles, but can still be successful. It emphasizes that good API design considers how the API will actually be used and iteratively incorporates feedback. APIs need not follow all REST principles to be effective if they meet the real needs of their users and are well designed.
Guide to Application Performance: Planning to Continued OptimizationMuleSoft
Supporting everything from mobile apps with thousands of concurrent users to global deployments processing millions of requests daily, Anypoint Platform has been put to test. In this session, MuleSoft experts will talk through case studies from our most demanding deployments and provide a best practice approach to designing and tuning applications for optimal performance.
Unilever: Driving Integration Speed and Agility - Frank Brandes, Director of ...MuleSoft
Owning over 400 brands in 190 countries, Unilever is one of the largest CPG companies in the world. The existing integration landscape includes over 12,000 interfaces, connecting over 1,600 endpoints and processing on average 1.6 million transactions per day. The current Center of Excellence (CoE)model has been successful at supporting the core business in a cost efficient and resilient way, however with the increase of disruptive technologies such as Cloud and Mobile a new capability was required to support the business requirements and increase agility. Mulesoft have partnered with Unilever to establish an in-house Adaptive Integration capability, operating a DevOps framework focused on driving self-service and API connectivity as part of a Centre for Enablement model. In this presentation Unilever will explain the approach they have taken, challenges and opportunities that have arisen as part of the transformation.
The Future of B2B: Applying API-Led Connectivity to B2B/EDI - Eric Rempel, CI...MuleSoft
B2B/EDI is often associated with staid, legacy technologies. Yet the business processes B2B/EDI supports are often those under most pressure to become more agile and flexible. Hear how industry leaders are meeting this challenge through applying API-led connectivity to B2B/EDI.
API Description Languages: Which is the Right One for Me?Akana
SOA Software Director of API Strategy, Laura Heritage, discusses new ways to describe and document APIs have emerged such as Swagger, RAML, API Blueprint and others, each taking a slightly different approach. Please join us in this webinar to hear how these description languages differ and how to choose right one for your API.
This document discusses enterprise application integration (EAI), which seeks to provide efficient, reliable data exchange between multiple enterprise applications. EAI involves integrating various types, including information portals, data replication, shared business functions, service-oriented architecture, and distributed business processes. The main challenges with integration are that networks are unreliable and slow, and any two applications are different. Common integration approaches include file transfer, shared databases, remote procedure invocation, and messaging. Messaging in particular allows for high-speed, asynchronous, and reliable integration through send-and-forget and store-and-forward communication.
Microservices is one of the hottest technology trends this year. In this presentation you'll see what microservices mean for your business, and learn about microservices best practices and implementation using Anypoint Platform.
This presentation will include:
-What is the microservices approach and how to achieve business agility with it
-How continuous delivery/continuous integration principles tie in with microservices
-How to implement microservices using Anypoint Platform
This presentation discusses Mule ESB and how to simplify integration. It briefly mentions a brief history of integration, information silos, SOA. It also highlights several integration patterns.
The document summarizes what Google learned over 10+ years of building cloud infrastructure and services, including embracing assumptions of running everything in the cloud, redundancy across data centers, and eventual consistency. It discusses trends that emerged like containers, microservices, serverless computing, and security becoming even more important. The key lessons are to not compromise on developer productivity, be open to alternatives but cautious of blindly following trends, and that security can never be too careful.
Google has invested $27 billion in data centers worldwide since 2014 to build the world's fastest and most powerful cloud infrastructure. In 2016, Google Cloud Platform experienced 36% year-over-year growth in bookings, a 50% increase in net customer count, and over 90 new features shipped. Google processes over 1 billion API calls per day and saw 58% year-over-year growth in Black Friday traffic.
Microservices - Death of the Enterprise Service Bus (ESB)? (Update 2016)Kai Wähner
Microservices are the next step after SOA: Services implement a limited set of functions. Services are developed, deployed and scaled independently.
Continuous Integration and Continuous Delivery control deployments. This way you get shorter time to results and increased flexibility. Microservices have to be independent regarding build, deployment, data management and business domains. A solid Microservices design requires single responsibility, loose coupling and a decentralized architecture. A Microservice can to be closed or open to partners and public via APIs. This session discusses the requirements, best practices and challenges for creating a good Microservices architecture, and if this spells the end of the Enterprise Service Bus (ESB). A live demo will show how middleware and Microservices complement each other using containers, continuous integration, REST services, and open source frameworks such as Cloud Foundry.
A live demo showed a "Microservices Middleware Architecture" using Cloud Integration (with Cloud Foundry PaaS), Integration and Services (with TIBCO BusinessWorks Container Edition), API Management / Open API (with Mashery) amd Log Management / IT Operations Analytics (ITOA, with Papertrail and LogLogic / Unity).
Thinking about incorporating digital trends like AR/VR, IoT, and cognitive analytics into your business? What should you think about? How can you derive enterprise value from these trends? Join Bill Briggs, the CTO of Deloitte Consulting, LLP, and Ross Mason, the founder and VP of Product Strategy at MuleSoft, who will talk about how organizations are using these trends and what you need to know to get started.
Microservices Done Right: Key Ingredients for Microservices SuccessApigee | Google Cloud
This document discusses microservices and keys to microservices success. It defines microservices as independently deployable services that work together. Microservices allow for agility, reuse, and productivity. The document outlines how enterprises are adopting microservices with containers, registries, auto-scaling and blue/green deployments. It emphasizes that REST APIs are a key ingredient for microservices success by enabling consumption and shielding consumers from complexity. The document also notes that microservices will fail without API management for issues like API sprawl, security threats and lack of visibility. It positions Apigee as providing the API layer and management capabilities needed for successful microservices.
Each and every business is unique. From healthcare to retail, manufacturing or finance — no two businesses
operate the same way. That’s why the Microsoft Cloud can be tailored to meet the needs of any enterprise.
It’s the cloud that helps drive unparalleled productivity. The cloud that turns massive streams of data into
actionable insight. The cloud that scales rapidly t o meet the growing demands of your business. And the
cloud that transforms a mobile workforce into a connected team. This is the cloud that’s built for your business.
The document describes design patterns for enterprise application integration (EAI). It discusses patterns related to service oriented architecture, notification, composition, testing, and optimization. Specific patterns covered include interoperability, service directory, event monitor, observer, publish/subscribe, and messaging bridge. The document provides goals, solutions, diagrams, and hints for each pattern to help with common integration problems.
Amazon began in 1994 as an online bookstore and has since grown to become the largest online retailer in America. It operates 7 websites globally and offers over 20 million products. There are four primary drivers of Amazon's growth: product focus, customer focus, technology focus, and distribution focus. Amazon deals with fluctuating demand through a multi-tier inventory model that aggregates inventory and purchases low demand items in response to customer orders to reduce costs.
This document provides a high-level overview of key components in telecom OSS/BSS systems. It discusses general concepts like numbering plans and call scenarios. It then summarizes the main components, including data collection, mediation, billing, SS7 monitoring, revenue assurance, and fulfillment/provisioning. The document provides brief explanations of the purpose and processes within each component.
Implementing an Effective Third-party & Vendor Risk Management ProgramKannan Subbiah
This document discusses implementing an effective third-party and vendor risk management program. It covers selecting a framework, the relationship lifecycle which includes strategy, due diligence, contracting, ongoing monitoring and re-evaluation. Key focus areas are scope, segmentation, due diligence, control systems, risk assessments, governance, organization, policy, tools and data. Recommendations include building a cross-functional team, being comprehensive without complexity, staying agile with risk-based intelligence, and complementing decision making with risk-based intelligence. The document also discusses compliance challenges, recovering from breach, next steps of integrating the approach and leveraging automation.
Developing & Deploying Effective Data Governance FrameworkKannan Subbiah
This is the slide deck presented at the Customer Privacy and Data Protection India Summit 2019 held in Mumbai, India. The specific topics touched upon are the guiding principles, Aligning with Data Architecture, Data Quality & Compliance.
Cyber fraud and Security - What risks does family office's face intoday's wo...Kannan Subbiah
Presented at the Private Wealth Management Summit 2017 held at Mumbai, India.
Security has to be considered as the foundation on which one can build a business. Gone are the days when we can build a perimeter, sit back and feel secure. In today’s digital environment we partner with others, we outsource, we have alliances, we let our customers into our systems and as we extend our networks.
In the digital economy, effective cyber security can mean the difference between a business’s success and its failure.
Big Bang Disruptions throw many enterprises out of business. Enterprises need to have a strategy to face these disruptive innovations. In this presentation we will go over some such disruptive innovations happened in the past to understand what it is and how some companies have faced these disruptions successfully. We sill also have a look at some of the potential disruptive technologies that are in the making.
This presentation was first delivered at the Monthly Meeting of ISACA, Chennai Chapter.
Risk management is a critical process for any organization. It involves identifying potential risks, assessing their likelihood and impact, and developing strategies to mitigate negative risks and maximize opportunities. The document provides an overview of risk management concepts and best practices. It defines risk, discusses why risk management is important, and outlines the basic steps of the risk management process including identification, analysis, evaluation, and monitoring of risks. Various risk assessment and prioritization techniques are also presented. The goal of risk management is to increase awareness and preparedness so organizations can achieve their objectives and improve outcomes.
This document provides an overview of cloud computing, including its evolution, definitions, characteristics, service models, deployment models, benefits, challenges, and case studies. It discusses the key technologies that enable cloud computing such as virtualization, web services, and software as a service. Several real-world examples of organizations using cloud computing are presented, including Google, Amazon, Facebook, IBM, Microsoft, Salesforce.com, and government agencies. The document also examines the economics of cloud computing and traditional data centers.
Social Computing – The Promise And The Perils FinalKannan Subbiah
Social media promises increased reach, engagement, and opportunities through connections with others. However, it also poses risks like privacy issues, data leaks, addiction, and cyber threats from phishing, malware, and state-sponsored attacks. While companies can benefit from social media, they must also address challenges of managing bandwidth, filtering inappropriate content, and ensuring employee productivity is not impacted. Organizations should have guidelines for safe social media use without compromising operations or security.