About DKh Al Obaidi

  In   IPSec,   specifically in Phase 1 IKE, the term "peer" refers to the entity that is communicating with the local device, and there are two different ways to identify the peer:     Peer Address:   This is the IP address or domain name that is used to identify the remote device with which the local device is communicating. The peer address is used to establish the initial connection between the two devices, and it is also used to route the encrypted traffic between them.   Peer Identification: This is a unique identifier that is used to authenticate the remote device during the IPSec negotiation process. The peer identification can be an IP address, a domain name, or a fully qualified domain name (FQDN). It is used to ensure that the remote device is authorized to communicate with the local device and to prevent unauthorized access.   Palo Alto VM firewall in Azure VPN site to site   If you are outside the Azure cloud (Azure will be doing the NAT) So the Peer Address and Peer Identification will be a bit confusing.   The main difference between peer address and peer identification is their purpose.   The peer address is used to establish the initial connection and to route the encrypted traffic, while the peer identification is used to authenticate the remote device during the IPSec negotiation process. Both are important for securing the IPSec communication and ensuring that only authorized devices are allowed to communicate with each. ... View more

As a SAML-based, single sign-on (SSO) login summary with most of SAML components in the picture below, I want to point out some important things that need to be done to make SAML work:   SAML is XML-based protocol used for exchanging authentication and authorization data between different parties, so we'll need the user's browser to handle that Any authentication needs a database to validate the users against it. You can store or create users in Identity Provider (IDP) as user's database, but most of the time you'll need to integrate IDP with Active Directory or Azure Active Directory Identity Provider (IDP) and Service Provider (SP) don't talk to each other during SAML user verification. To make SAML work, you need to connect IDP with SP ahead of time. IDP and SP need to exchange metadata and get SSL certification for this integration to work. The SP and IDP must establish a trust relationship, which involves exchanging metadata that includes information about each other's endpoints, public keys, and other configuration details   SAML (Security Assertion Markup Language) protocol components and messages based to single sign-on (SSO):   Identity Provider (IDP): The system responsible for authenticating users and issuing SAML assertions that contain information about the user's identity and attributes Service Provider (SP): The system that provides access to protected resources or applications and that relies on SAML assertions issued by the IDP to authenticate users Assertion Consumer Service (ACS): A web endpoint on the SP that receives and processes SAML responses from the IDP SAML Request: A message sent by the SP to the IDP requesting authentication and authorization for a user SAML Response: A message sent by the IDP to the SP containing a SAML assertion that authenticates the user and provides information about their identity and attributes       ... View more

  Over ninety-five percent of end users report experiencing unanticipated application downtime, which causes businesses to lose valuable productivity. Find and fix problems with the user experience using autonomous digital experience management, all before those problems have an effect on your company.     ... View more

  Watch this video to learn a step-by-step process for configuring authentication in Prisma Access using SAML Microsoft Azure.     ... View more

Prisma Access / Active Directory / Okta    Learn how to integrate Prisma Access with Okta by using SAML protocol in this video.      ... View more

Watch this video to learn how to set up a VPN (site-to-site) between Prisma Access and AWS Cloud.   ... View more

  Prisma Access with Azure   These two videos show you how to build the VPN Site to Site (Remote Networks) between Prisma Access and Azure Cloud.   Part 1     Part 2       ... View more

    Let’s walk through how to set up a web server for the “IP Change Event Notification URL option” in Prisma Access.    1. Install Linux Ubuntu in Azure or in anywhere (but should be public access).   2. Install the simple python command as below to make the HTTP web server.    paloalto@URL-Server:~$ sudo curl -L https://raw.githubusercontent.com/nickjj/webserver/v0.2.0/webserver -o /usr/local/bin/webserver && sudo chmod +x /usr/local/bin/webserver     3. Turn on the HTTP web server use this command (you can change the port number).   paloalto@URL-Server:~$ webserver 0.0.0.0:5000           4. Now, in Prisma Access, you need to add the IP/URL of the server to the IP Change Event Notification URL option:             5. Now any IP change, even in Prisma Access, the HTTP server will get a notification like what we see below:         All notification will be in Json and under three categories:   Add/Delete/Updates         Check out this video on IP Change Event Server Steps.   Resources:  Web Server github Retrieve the IP Addresses for Prisma Access   Special thanks to Karam Hanna for his amazing help.    Thank you for reading! ... View more