DOCSLIB.ORG

Cisco Firepower Threat Defense REST API Guide Americas Headquarters Cisco Systems, Inc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cisco Firepower Threat Defense REST API Guide Americas Headquarters Cisco Systems, Inc Cisco Firepower Threat Defense REST API Guide Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version. Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R) © 2017–2021 Cisco Systems, Inc. All rights reserved. CONTENTS CHAPTER 1 About the Firepower Threat Defense REST API 1 Audience for This Programming Guide 1 Supported HTTP Methods 1 The Base URL for the API 2 Securing SSL/TLS Communications for the FTD API 2 Determining the Supported API Versions 3 API Version Backward Compatibility 3 Version History for the Firepower Threat Defense REST API 4 CHAPTER 2 The API Explorer 7 Opening the API Explorer 7 Finding Your Way Around API Explorer 8 Viewing Documentation About a Resource 8 Finding the Object ID (objId) and Parent ID 10 Viewing the Error Catalog And Evaluating Error Messages 10 CHAPTER 3 General Process for Using the REST API 13 General Process for Using the REST API 13 CHAPTER 4 Authenticating Your REST API Client Using OAuth 15 Overview of the API Client Authentication Process 15 Requesting a Password-Granted Access Token 17 Requesting a Custom Access Token 19 Using an Access Token on API Calls 21 Refreshing an Access Token 21 Revoking an Access Token 23 Cisco Firepower Threat Defense REST API Guide iii Contents CHAPTER 5 Configuring External Users for the API 25 Define Authorization Rights in the RADIUS User Accounts 26 Define the RADIUS Servers 26 Create a AAA Server Group for the RADIUS Servers 28 Establish the AAA Server Group as an Authentication Source for HTTPS Access 30 Verify External User Access 33 CHAPTER 6 Using the Methods and Resources 37 Trying a Method and Interpreting the Results 37 GET: Obtaining Data from the System 39 POST: Create a New Object 41 PUT: Modify an Existing Object 43 DELETE: Remove a User-Created Object 45 CHAPTER 7 Deploying Configuration Changes 47 Deploying Configuration Changes 47 CHAPTER 8 Configuration Import/Export 49 About Configuration Import/Export 49 What is Included in the Export File 49 Comparing Import/Export and Backup/Restore 50 Strategies for Import/Export 50 Guidelines for Configuration Import/Export 51 Importing and Exporting Configurations 51 Export the Configuration 51 Check the Status of the Export Job 54 Download the Export File 54 Edit the Exported Configuration File 55 Minimum Configuration File Requirements 56 Basic Structure of Identity Wrapper Objects 56 Example: Editing a Network Object for Import Into a Different Device 57 Upload the Import File 58 Import the Configuration and Check Job Status 59 Cisco Firepower Threat Defense REST API Guide iv Contents Delete Unneeded Import/Export Files 62 CHAPTER 9 For More Information and Examples 65 For More Information and Examples 65 Cisco Firepower Threat Defense REST API Guide v Contents Cisco Firepower Threat Defense REST API Guide vi CHAPTER 1 About the Firepower Threat Defense REST API You can use the Firepower Threat Defense REpresentational State Transfer (REST) Application Programming Interface (API), over HTTPS, to interact with a FTD device through a client program. The REST API uses JavaScript Object Notation (JSON) format to represent objects. Firepower Device Manager includes an API Explorer that explains all of the resources and JSON objects available for your programmatic use. The Explorer provides detailed information about the attribute-value pairs in each object, and you can experiment with the various HTTP methods to ensure you understand the coding required to use each resource. The API Explorer also provides examples of the URLs required for each resource. You can also find reference information and examples online at https://developer.cisco.com/site/ ftd-api-reference/. The API is has its own version number. There is no guarantee that a client designed for one version of the API will work for a future version without error or without requiring changes to your program. • Audience for This Programming Guide, on page 1 • Supported HTTP Methods, on page 1 • The Base URL for the API, on page 2 • Securing SSL/TLS Communications for the FTD API, on page 2 • Determining the Supported API Versions, on page 3 • API Version Backward Compatibility, on page 3 • Version History for the Firepower Threat Defense REST API, on page 4 Audience for This Programming Guide This guide is written on the assumption that you have a general knowledge of programming and a specific understanding of REST APIs and JSON. If you are new to these technologies, please first read a general guide on REST APIs. Supported HTTP Methods You can use the following HTTP methods only. The other methods are not supported. • GET—To read data from the system. • POST—To create new objects. Cisco Firepower Threat Defense REST API Guide 1 About the Firepower Threat Defense REST API The Base URL for the API • PUT—To modify existing objects. When using PUT, you must include the entire JSON object. You cannot selectively update individual attributes within an object. • DELETE—To remove a user-defined object. The Base URL for the API The easiest way to determine the base URL for a given FTD device is to try out a GET method in the API Explorer, and simply delete the object part of the URL from the result. For example, you can do a GET /object/networks, and see something similar to the following in the returned output under Request URL: https://ftd.example.com/api/fdm/v1/object/networks The server name part of the URL is the hostname or IP address of the FTD device, and will be different for your device in place of “ftd.example.com.” In this example, you delete /object/networks from the path to get the base URL: https://ftd.example.com/api/fdm/v1/ All resource calls use this URL as the base for the request URL. If you changed the HTTPS data port, you must include the custom port in the URL. For example, if you changed the port to 4443: https://ftd.example.com:4443/api/fdm/v1/ The "v" element in the URL is the API version, and this will typically change with the software version. For example, the API version for FTD version 6.3.0 is v2, so the base URL would be: https://ftd.example.com/api/fdm/v2/ Note Starting with FTD 6.4, you can avoid the need to update the path in your API calls by using latest instead of the v element in the path. For example, https://ftd.example.com/api/fdm/latest/. The latest alias resolves to the most recent API version supported by the device. In the API Explorer, if you scroll to the bottom of the page, you can see information on the base URL (without the server name) and API version. Securing SSL/TLS Communications for the FTD API FTD devices come with a self-signed certificate so that you can initiate HTTPS communications with the device. However, because the certificate is not signed by a known Certificate Authority (CA), any SSL/TLS access attempt will consider the connection insecure.
Load more

Recommended publications
  • Release 0.0.2 Hypothes.Is Project and Contributors
    The h Documentation Release 0.0.2 Hypothes.is Project and contributors Sep 27, 2021 Contents 1 Contents 3 Index 25 i ii The h Documentation, Release 0.0.2 h is the web app that serves most of the https://hypothes.is/ website, including the web annotations API at https: //hypothes.is/api/. The Hypothesis client is a browser-based annotator that is a client for h’s API, see the client’s own documentation site for docs about the client. This documentation is for: • Developers working with data stored in h • Contributors to h Contents 1 The h Documentation, Release 0.0.2 2 Contents CHAPTER 1 Contents 1.1 The Hypothesis community Please be courteous and respectful in your communication on Slack (request an invite or log in once you’ve created an account), IRC (#hypothes.is on freenode.net), the mailing list (subscribe, archive), and GitHub. Humor is appreciated, but remember that some nuance may be lost in the medium and plan accordingly. If you plan to be an active contributor please join our mailing list to coordinate development effort. This coordination helps us avoid duplicating efforts and raises the level of collaboration. For small fixes, feel free to open a pull request without any prior discussion. 1.2 Advice for publishers If you publish content on the web and want to allow people to annotate your content, the following documents will help you get started. 1.2.1 Generating authorization grant tokens Warning: This document describes an integration mechanism that is undergoing early-stage testing.
    [Show full text]
  • Hacking JSON Web Token (JWT) - 101-Writeups
    Hacking JSON Web Token (JWT) - 101-writeups ... https://medium.com/101-writeups/hacking-json... Hacking JSON Web Token (JWT) Rudra Pratap Follow May 3, 2018 · 5 min read Hey, Well this is my first writeup and there might be ton of mistakes as i go along writing it out so please give me feedback so that i can work over it. So lets start! JWT ... 0x01 JWT work�low Starting with JWT, it is a very lightweight specification 1 of 13 8/21/19, 10:35 AM Hacking JSON Web Token (JWT) - 101-writeups ... https://medium.com/101-writeups/hacking-json... This specification allows us to use JWT to pass secure and reliable information between users and servers. JWT is often used for front-end and back-end separation and can be used with the Restful API and is often used to build identity authentication mechanisms. Take an example of vimeo.com , which is one of the biggest video hosting companies as per my knowledge. ... Figure 1 2 of 13 8/21/19, 10:35 AM Hacking JSON Web Token (JWT) - 101-writeups ... https://medium.com/101-writeups/hacking-json... Figure 2 When a user enters his/her credentials, a post request is sent (check Figure 1) after which the credentials are validated. If they are a correct combo then the user is presented with response having a JWT token as seen in Figure 2. ... Example JWT : eyJraWQiOiJrZXlzLzNjM2MyZWExYzNmMTEzZjY0OWRjOTM4OW RkNzFiODUxIiwidHlwIjoiSldUIiwiYWxnIjoiUlMyNTYifQ.eyJzdWIiOi JkdWJoZTEyMyJ9.XicP4pq_WIF2bAVtPmAlWIvAUad_eeBhDOQe2 MXwHrE8a7930LlfQq1lFqBs0wLMhht6Z9BQXBRos9jvQ7eumEUF WFYKRZfu9POTOEE79wxNwTxGdHc5VidvrwiytkRMtGKIyhbv68du FPI68Qnzh0z0M7t5LkEDvNivfOrxdxwb7IQsAuenKzF67Z6UArbZE8 odNZAA9IYaWHeh1b4OUG0OPM3saXYSG- Q1R5X_5nlWogHHYwy2kD9v4nk1BaQ5kHJIl8B3Nc77gVIIVvzI9N_ klPcX5xsuw9SsUfr9d99kaKyMUSXxeiZVM-7os_dw3ttz2f- TJSNI0DYprHHLFw Now whenever a user accesses something, the request which are made are slightly different having a new header authorization: jwt 3 of 13 8/21/19, 10:35 AM Hacking JSON Web Token (JWT) - 101-writeups ..
    [Show full text]
  • Openair XML API Reference Guide
    XML API Reference Guide April 10, 2021 Copyright © 2013, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Precompiler Session 01 - Tuesday 8:00 Machine Learning: Taking Your ML Models to Android and Ios Wes Eklund
    PreCompiler Session 01 - Tuesday 8:00 Machine Learning: Taking your ML Models to Android and iOS Wes Eklund Once you've developed a kickass Machine Learning model, you need a way to get that model to your computing devices (phones) to start doing your predictions! Most Machine Learning projects in production will 'train' the model on cloud servers, then 'deploy' the model to an API server or mobile device. This session will introduce the attendee on using TensorFlow Serving and Apple CoreML to deploy Machine Learning models to a mobile app. Prerequisites: Download Here Build a Natural Language Slack Bot for your Dev Team Michael Perry Many project teams use Slack as a means of communication with one another. Why not also use it to communicate with your infrastructure? Invite a helper into your conversation that can perform routine tasks tirelessly, conversationally, and interactively. In this 4 hour workshop, you will build a Slack bot that understands natural language and integrates with your DevOps pipeline. You will use the Slack Events API to receive messages, and the Slack Web API to send them. You will use LUIS to interpret language and extract intent. You will execute actions against the Visual Studio Team Services Web API in response to user requests, and subscribe to Webhooks to notify your team of important events. In the end, you will have a new member of your team who can help you with your build and release pipeline. Workshop outline: Slack API Authorization - OAuth and API key verification Events API - respond to posts Web
    [Show full text]
  • On the Security of Single Sign-On
    On the Security of Single Sign-On Vladislav Mladenov (Place of birth: Pleven/Bulgaria) [email protected] 30th June 2017 Ruhr-University Bochum Horst G¨ortz Institute for IT-Security Chair for Network and Data Security Dissertation zur Erlangung des Grades eines Doktor-Ingenieurs der Fakult¨atf¨urElektrotechnik und Informationstechnik an der Ruhr-Universit¨atBochum First Supervisor: Prof. Dr. rer. nat. J¨org Schwenk Second Supervisor: Prof. Dr.-Ing. Felix Freiling www.nds.rub.de Abstract Single Sign-On (SSO) is a concept of delegated authentication, where an End- User authenticates only once at a central entity called Identity Provider (IdP) and afterwards logs in at multiple Service Providers (SPs) without reauthenti- cation. For this purpose, the IdP issues an authentication token, which is sent to the SP and must be verified. There exist different SSO protocols, which are implemented as open source libraries or integrated in commercial products. Google, Facebook, Microsoft and PayPal belong to the most popular SSO IdPs. This thesis provides a comprehensive security evaluation of the most popular and widely deployed SSO protocols: OpenID Connect, OpenID, and SAML. A starting point for this research is the development of a new concept called malicious IdP, where a maliciously acting IdP is used to attack SSO. Generic attack classes are developed and categorized according to the requirements, goals, and impact. These attack classes are adapted to different SSO proto- cols, which lead to the discovery of security critical vulnerabilities in Software- as-a-Service Cloud Providers, eCommerce products, web-based news portals, Content-Management systems, and open source implementations.
    [Show full text]
  • Demystifying Tokens for Securing Enterprise Apis
    DEVELOPING AND CONNECTING ISSA Demystifying Tokens for CYBERSECURITY LEADERS GLOBALLY Securing Enterprise APIs Demystifying Tokens for Securing Enterprise APIs By Sandeep Jayashankar – ISSA member Delaware Chapter and Subin Thayyile Kandy – ISSA member Delaware Chapter This article is mainly designed for a software architect to help understand the problems tokens tend to solve, with illustrations of different types of tokens in use. The authors also explain the token implementation methods for an enterprise API mechanism and provide security best practices to be taken care of when implementing the same. Abstract able products, both as a software and a service, to handle the authentication security controls. The security community has Tokens have been the de-facto means that support scalable striven to set many authentication policy definitions, such as and performance-focused security solutions in the current password policies, user lockout policies, captcha frameworks, technological environments. There are currently many op- and provided many scan engines to check the implemented tions and operation modes for anybody thinking of imple- authentication policies. Enterprise organizations have priori- menting a token-based security measure with support of tized their strategic plans concerning security by utilizing the cryptographic mechanisms. With the web-attack landscapes best products to support the applications’ authentication and changing to APIs, and with APIs managed as a decoupled password handling requirements. data handling entity, APIs need to have stringent authori- zation decision engines that ensure an authorized entity re- Implementing single sign-on with compulsory multi-factor quests each data retrieval. This article is mainly designed for authentication sequences has become a de facto for appli- a software architect to help understand the problems tokens cations and web components in an enterprise environment.
    [Show full text]
  • Angularjs Passing Jwt Every Request
    Angularjs Passing Jwt Every Request Uncompassionate and jetty Gunter still understand his free-spokenness compositely. Strawlike Julie bepaints aught or boodles dumbly when Andrey is imploring. Lightless and unquoted Sloane pent his tinhorn skelly corroding aimlessly. Well to test various authorization server renders is needed and every request Is fraud possible and implement SSO with OAuth? I thought that we an angular default feature and asked in angularjs. ELI5 how JWT works angularjs Reddit. The jwt based on every http interceptor its main application file: we pass the! Token-based Authentication in Angular 6 with ASPNET Core. We pass it also easier to jwt signature as a user controlled access any errors were supposed to every http request and passing headers. This means that for every dream you send by any firm the secured API endpoints you urge to pass rush a valid JWT in humble request Header so that further back-end. Introducing OwinStatelessAuth with Jonathan Channon Blog. In JWT, the header actually comes before the payload. Call Userlogin to request content access token without the client application on. Angular project here i pass this is handled by default to medium members of mars, and password we have the interceptor? CORS is a W3C Recommendation supported by all modern browsers. Token-Based Authentication for AngularJS and Laravel Apps. Ultimately, each API is honey to predict different requirements. You passing them. Return later an user gets applied are two sections describe what they give them to reuse existing set up the signature verification signature. CSRF attack in progress. For me please make target like this.
    [Show full text]
  • Big Code Infrastructure for Building Tools to Improve Software Development
    Big Code Infrastructure for Building Tools to Improve Software Development Oscar´ Rodr´ıguezPrieto PhD Supervisor Prof. Francisco Ort´ınSoler Department of Computer Science University of Oviedo A thesis submitted for the degree of Doctor of Philosophy Oviedo, Spain June 2020 Acknowledgements This work has been partially funded by the Spanish Department of Science and Technology, under the National Program for Research, Development and Innovation (project RTI2018-099235-B-I00). We have also received funds from the University of Oviedo, through its support to official research groups (GR-2011-0040). I was awarded an FPU grant by the Spanish Department of Science and Technology (grant number FPU15/05261). The objective of these grants is to support graduate students wishing to pursue a PhD de- gree. A PhD dissertation is proposed to be undertaken by the appli- cant, within a research group and supervised by a tenure researcher. Part of the research discussed in this dissertation has also been funded by the European Union, through the European Regional Development Funds (ERDF); and the Principality of Asturias, through its Science, Innovation Plan (grant GRUPIN14-100). The research work in this dissertation was partially done during my research stay at the Computer Laboratory of the University of Cam- bridge (UK), under the supervision of Professor Alan Mycroft. I thank all the people of the Computer Laboratory for their warm welcome and their generous hospitality. Abstract The use of source code repositories such as GitHub, SourceForge and Bitbucket has significantly risen in the last decade. According to GitHub, on November 2018 this code hosting platform reached 100 million repositories; on 2019, 44 million new repositories were created.
    [Show full text]
  • Authentication and Authorization for Constrained Environments
    Authentication and Authorization for Constrained Environments Master Thesis Urs Gerber August 2018 Thesis supervisors: Prof. Dr. Jacques Pasquier-Rocha and Arnaud Durand Software Engineering Group Software Engineering Group Department of Informatics University of Fribourg (Switzerland) Acknowledgements I want to thank my family and friends for their continuous support during the duration of this project. It is due to them that I was able to participate in this master class. I also want to express my thanks to Arnaud Durand and Professor Pasquier-Rocha, my thesis supervisors, who have provided me with the opportunity to work on this project and always pointed me in the right direction during the course of this project. i Abstract In this work, we present a proof-of-concept implementation for the protocols and enti- ties encompassed by the Authentication and Authorization for Constrained Environments (ACE) framework proposed in a working document of the Internet Engineering Task Force. The ACE framework is designed as an extension to the OAuth 2.0 authoriza- tion framework, which defines protocols how clients access protected resources on remote servers on behalf of a resource owner. The ACE framework adapts the protocols and prim- itives for use in the Internet of Things (IoT) where networking nodes can be very limited in terms of processing power and memory capacity. We provide a Python implementa- tion for all ACE entities, i.e. authorization server, resource server and client. In order to achieve confidential communication between the client and resource server, we imple- ment an application layer security protocol based on the Diffie-Hellman key exchange.
    [Show full text]
  • Spice Program Open Source 2015 Learnings
    Spice Program Open Source 2015 learnings Please see this Futurice Spice Program blog post to learn the context for this list. ​ ​ Learned even more about practical problems in measuring time. Direct uploads from browser to AWS S3. Basics of Polymer. React + Redux (lots of it). Basic info about Google Cloud Services. Practical usage of Google Cloud Storage (the Google's S3 equivalent). Heroku Pipelines. Improved & more modular Angular application structure formation. Webpack, JSON Web Token implementation on the backend, and ES6. Actually learning how Promises should be used in JavaScript. Some knowledge about Dokku, the host­it­yourself­Heroku. Got practical experience and more understanding about Node.js, npm, and bacon.js. How the Azure Web App continuous deployment works. A bit on how Travis CI operates under the hood. How to make Joomla templates. Learned about Let's Encrypt on Apache with vhosts. Learned more about Web MIDI API and RxJS. Also more about ES6 and setting up a compact development environment for that. Learned basics of RxJS. Learned a lot about creating a reusable library with JS/browserify. Learned some Cycle.js. Learned a little about Node.js testing. Learned the EMV chip card specification on very detailed level by implementing large part of the specification. I'm using the EMV knowledge on daily basis in my current client project. Improved my Clojure language skills. Learned to work with the Go programming language. Wrote an OSS tool that I later then used in a customer project. I learned better ways to use Dagger 2 in Android and trial and evaluate other app architectural patterns based around this.
    [Show full text]
  • CICS TS for Z/OS: CICS Security Guide Chapter 1
    CICS Transaction Server for z/OS 5.6 CICS Security Guide IBM Note Before using this information and the product it supports, read the information in Product Legal Notices. This edition applies to the IBM® CICS® Transaction Server for z/OS®, open beta (product number 5655-YV15655-BTA ) and to all subsequent releases and modifications until otherwise indicated in new editions. The IBM CICS Transaction Server for z/OS, open beta may be referred to in the product and documentation as CICS Transaction Server for z/OS, 6.1 . © Copyright International Business Machines Corporation 1974, 2021. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this PDF.......................................................................................................v Chapter 1. What does security mean for CICS?....................................................... 1 Chapter 2. CICS security is a team sport.................................................................7 Chapter 3. How it works: identification in CICS.......................................................9 Identity propagation.................................................................................................................................. 15 Chapter 4. How it works: authentication in CICS...................................................19 Which authentication method can I use with CICS access methods?..................................................... 25 Passwords and passphrases....................................................................................................................
    [Show full text]
  • MEAN Stack - JSON Web Token Tworzenie Serwisów Web 2.0
    MEAN Stack - JSON Web Token Tworzenie serwisów Web 2.0 dr inż. Robert Perliński [email protected] Politechnika Częstochowska Instytut Informatyki Teoretycznej i Stosowanej 19 listopada 2018 MEAN Stack - JSON Web Token 1/37 Plan prezentacji 1 JSON Web Token Budowa i działanie JWT JWT Header JWT Payload JWT Signature Jak JWT chroni dane? JWT w Node.js i Express.js Pakiet jwt-async Pakiet express-jwt 2 Źródła MEAN Stack - JSON Web Token 2/37 https://jwt.io/ JSON Web Token to otwarty, przemysłowy standard RFC 7519, który definiuje zwięzyły i samowystarczalny sposób na bezpiecznie przekazanie informacji pomiędzy dwiema stronami w formie obiektu JSON. Taka przekazana informacja może być zweryfikowana ponieważ jest cyfrowo podpisana. JWT może być podpisany używając tajnego klucza (algorytm HMAC) albo przy pomocy pray kluczy publiczny/prywatny używając algorytmu RSA. jwt.io pozwala na dekodowanie, weryfikację i generowanie JWT. MEAN Stack - JSON Web Token 3/37 Cechy JWT Mały rozmiar - pozwala na przesyłanie tokentów: w adresie URL, jako parametry metody POST, w nagłówku protokołu HTTP. Samodzielny - JWT zawiera wszystkie potrzebne do weryfikacji informacje, nie ma potrzeby dodatkowego łączenia się np. z bazą danych. Kiedy warto używać? Uwierzytelnienie - najczęstszy scenariusz dla JWT. Jedno zalogowanie się wystarczy do uzyskania JWT i wielokrotnego dostępu do danych przy użyciu tokenu. Można łatwo używać nawet dla wielu domen. Wymiana informacji - dobrze nadaje się w wymianie informacji między stronami, może być podpisany z użyciem pary kluczy publiczny/prywatny. Mamy pewność nadawcy. Mamy też pewność, że odebrane dane (nagłówek i ładunek) są nienaruszone. MEAN Stack - JSON Web Token 4/37 JSON Web Token JSON Web Token to obiekt JSON zdefiniowany według standardu RFC 7519, który pozwala w bezpieczny sposób na reprezentację zbioru informacji między dwiema stronami.
    [Show full text]