Best tcs template for presentation

TCS Presentation 1

Transcript: DISTRIBUTED SYSTEMS Security Patterns Presented by Naga Manoj Bhaskara What is...? What is...? Distributed System Definition Definition Virtually all large computer-based systems are now distributed systems. Information processing is distributed over several computers rather than confined to a single machine Key Points We will be discussing Characteristics of Distributed Systems Issues with Distributed Systems Security Issues Security Patterns Value of Security Patterns Distributed Systems Characteristics and Issues of Distributed Systems Characteristics Distributed Systems Characteristics Resource Sharing : Sharing of hardware and software resources Openness : Use of equipment and software from distributed vendors Concurrency : Concurrent processing to enhance performance Scalability : Increased throughput by adding new resources Fault tolerance: The ability to continue in operation after a fault has occurred. Distributed Systems Issues Complexity : They are more complex because different parts of the system are independently managed as is the network. There is no single authority in charge of the system so top-down control is impossible. When a system is distributed, the number of ways that the system may be attacked is significantly increased. If a part of the system is successfully attacked then the attacker may be able to use this as "back door" into other parts of the system. Privacy Concerns Issues Vulnerabilities One of the important reason for system weakness is that security is built as add-on, parts of the system are secured using specific mechanisms but there is rarely a global security analysis for complete system. Different Organizations may own different part of system. These organizations may have mutually incompatible security policies and security mechanisms. System Vulnerabilities Security Patterns Pattern A pattern is a solution to a recurring problem in a specific context A security pattern solves a security problem, usually how to control a threat Pattern 1 Pattern 1 Separate Authorization From Access Control – Enhances scalability – Eases crossing administrative boundaries Existing Systems • User needs credential per service – different types of credentials – different rules for use – too many passwords • Every service needs to do – authentication – authorization – access control • Too many updates • Authentication does not tell what service needs to know Access Pattern Service only needs simple access control mechanisms An access right can be meaningful to one service Rules can be registered by third party Admits multiple management schemes for one service Can add new service, types of access, etc. without affecting management mechanisms Example Example Pattern 2 Pattern 2 Mediate between Client and Service – Enforces audit policies – Simplifies access control decisions Existing Systems • Each service needs to – authenticate users – make authorization decisions – produce audit trail – protect against malicious or erroneous users • Common library linked with service – guaranteeing proper use – rolling forward versions Mediation Pattern Mediator provides – trusted path – additional meta data – mutual anonymity – audit information Service and client don’t have to trust each other directly Mediator can translate authorization information into a form meaningful to service Mediator can verify protocol adherence Example Operating system acts as the mediator for the user requesting file. Example Pattern 3 Pattern 3 Use a Service-side Proxy for Remote Users – Improves control over remote parties – Prevents some attacks – Limits damage done when attack succeeds Existing Systems • Every service subject to a variety of network attacks • Successful attack can do anything service can do • Crashing server cuts off all users • Service must – deal with authentication, authorization, access control – enforce machine-specific policies Proxy Pattern Crashing proxy cuts off attacker Protection domain of remote user under local control Proxy can be smart and filter requests Smarts added to proxy implementation protect all services Example ATM Machine with remote proxy server Example Value of Security Patterns Value of Security Patterns Conclusion Conclusion Security patterns are a useful tool to build secure systems Patterns are also valuable for evaluating existing systems and for teaching security concepts Patterns cannot prevent attacks that happen through code flaws but can make their effect much less harmful; in any case, they can be complemented with code analysis Patterns can lead to building strong systems, a more effective and ethical approach than retaliation Conclusion THANK YOU! References Uzunov, A. V., Fernandez, E. B., & Falkner, K. (2012). Securing distributed systems using patterns: A survey. Computers & Security, 31(5), 681-703. https://doi.org/10.1016/j.cose.2012.04.005 Karp, A. H., & Smathers, K. (2003, February 25). Three Design Patterns for Secure Distributed Systems. CiteSeerX.

Tcs Template For Presentation

Create your presentation by reusing one of our great community templates.

TCS Scholarship Presentation

TCS Presentation

TCS Presentation 1

Template for presentation

TCS presentation

TCS CASE PRESENTATION

TCS FINAL PRESENTATION

TCS CASE PRESENTATION

Explore our templates for more presentation inspiration

Grant Proposal Presentation for NonProfit & Education | Prezi

Lesson Plan - Board

Best Executive Presentation Template to Customize | Prezi

Report - EDU