Mule enterprise security
- 1. Agenda Introducing Mule Enterprise Security Drill-down into – Mule STS OAuth 2.0 Provider – Mule Credential Vault – Mule Security Filter Processors Brief Overview of other New Mule Enterprise Security Features Wrap-up and Q&A All contents Copyright © 2011, MuleSoft Inc. 2
- 2. Mule Enterprise Security - Benefits All contents Copyright © 2011, MuleSoft Inc. 3 1 - Protect access to your Mule application end-points and the services they access 2 - Maintain the confidentiality of data used and emitted by your mule flows 3 - Guard your Mule interfaces against security attacks SOA Mobile APIs SaaS Integration
- 3. Mule Enterprise Security All contents Copyright © 2011, MuleSoft Inc. 4
- 4. Mule STS OAuth 2.0 Provider - Why Protect your APIs with OAuth Enables credentials to only be shared with a single, central entity All contents Copyright © 2011, MuleSoft Inc. 5 Applications (OAuth Clients) APIs Exposed by Mule Application (OAuth Service Provider) Application End-Users Mobile Apps Web Apps Mule Cloud Connector Apps OAuth Protected
- 5. Mule STS OAuth 2.0 Provider - What Mule can act as an OAuth 2.0 provider OAuth element protects flow Supports for all OAuth 2.0 grant types Supported end-points – HTTP/S, Jetty, Servlet, Web Services All contents Copyright © 2011, MuleSoft Inc. 6
- 6. Mule Credential Vault - Why Access external end-points without exposing their access credentials – Store credentials in encrypted format All contents Copyright © 2011, MuleSoft Inc. 7
- 7. Mule Credential Vault - What Encrypt content of Mule application property files Mule Studio provides property value encryption tool Values decrypted upon access from Mule Flows All contents Copyright © 2011, MuleSoft Inc. 8
- 8. Mule Security Filter Processors - Why Whitelist a specific set or range of IP addresses Enable expiry policy using message time-stamp All contents Copyright © 2011, MuleSoft Inc. 9
- 9. Mule Security Filter Processors - What Use Mule security filter processors to – Set filtering needs and parameters Support for – IP filtering (single, range, and CIDR) – Message expiry filtering All contents Copyright © 2011, MuleSoft Inc. 10
- 10. Mule Enterprise Security – Features Overview All contents Copyright © 2011, MuleSoft Inc. 11 Feature Description Mule Secure Token Service (STS) – OAuth 2.0 Provider Enables a Mule server to act as an OAuth 2.0 authentication provider to protect specific mule flows. Mule Credential Vault Encrypt sensitive values (e.g. passwords) in your Mule message flows. Mule Security Filter Processors Allow filtering of messages based on security criteria: IP based and expiry based. Mule Digital Signature Processors Simplifies the signing and verification of XML Signatures within Mule flows. Mule Message Encryption Processors Easily encrypt and decrypt sensitive data in Mule messages.
- 11. Mule Enterprise Security All contents Copyright © 2011, MuleSoft Inc. 12 1 - Protect access to your Mule application end-points and the services they access 2 - Maintain the confidentiality of data used and emitted by your mule flows 3 – Guard your Mule interfaces against security attacks SOA Mobile APIs SaaS Integration
Editor's Notes
- #2: Slide 2: Housekeeping items Just a couple of housekeeping items before we get started: This session is being recorded and will be available immediately following the webinar You can download the slides right now from the “attachments” tab If you have content or technical questions, please feel free to ask them at any time by typing them into and sending them via the question button above the slides. We will answer questions at the end of the session but please feel free to send over questions as they arise. If we don’t get to your question or if you have any detailed use-case specific questions, you can submit them to our team of experts at tinyurl.com/askmulesoft
- #4: Go over the MES benefits Then mention the fact that these benefits span solution areas
- #6: Safe Access as per OAuth: - Allows you to protect any HTTP based interface for access – usually used for REST APIs Temporary and restricted access – Access is controlled through OAuth tokens which can have an expiry date and limited scope to allow for RBAC Often consumed and used by Mobile apps
- #9: Key for decrypting the properties is provided as a system property: <secure-property-placeholder:config key="${runtime.property}" location="test.qa.properties"/> ./mule -D-Mruntime.propery=mySecretKey
- #10: Useful for security gateway scenarios
- #13: Go over the MES benefits Then mention the fact that these benefits span solution areas
- #14: Slide 2: Housekeeping items Just a couple of housekeeping items before we get started: This session is being recorded and will be available immediately following the webinar You can download the slides right now from the “attachments” tab If you have content or technical questions, please feel free to ask them at any time by typing them into and sending them via the question button above the slides. We will answer questions at the end of the session but please feel free to send over questions as they arise. If we don’t get to your question or if you have any detailed use-case specific questions, you can submit them to our team of experts at tinyurl.com/askmulesoft