This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About Justin_Payne
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- LIVEcommunity
- About Justin_Payne
12-22-2021
5Posts
0Likes
0Solutions
Dec 22, 2021Last Visited
User
Activity
User
Profile
Latest posts by Justin_Payne
| Subject | Views | Posted |
|---|---|---|
| 997 | 06-24-2021 07:46 AM | |
| 1915 | 03-12-2020 09:47 AM | |
| 6439 | 01-08-2020 11:28 AM | |
| 2252 | 12-19-2019 09:11 AM | |
| 2307 | 12-16-2019 06:27 AM |
User Badges
Community Statistics
| Member Since | 06-15-2017 07:47 AM |
| Date Last Visited | 12-22-2021 08:05 AM |
| Posts | 5 |
03-10-2022
06:19 AM
Justin, Did you ever find a solution to this?
... View more
07-04-2021
12:19 AM
It is hard to dive into that without the logs. I suggest deleting all of the current MS integrations instances, and try re create new ones with *different* instance names. please visit here for further explanation on the auth process and suggestions: https://xsoar.pan.dev/docs/reference/articles/microsoft-integrations---authentication
... View more
03-23-2020
06:34 AM
You can leverage our Audit Policies with something along the below lines, in terms of RQL. event where operation IN ( 'AssociateElasticIp', 'RegisterElasticIp', 'UpdateElasticIp' ) This will create an alert anytime you have a user actually make a change to the EIP. Another way you can achieve this is by simply checking for instances that have a public IP. Though this will return existing systems that should or are known to have public IPs. config where api.name = 'aws-ec2-describe-instances' AND json.rule = publicIpAddress exists and publicIpAddress is not empty
... View more
01-09-2020
05:34 AM
Hi, In our case, the upgrade of the plugin has solve the registration issue. Regards.
... View more
12-16-2019
06:33 AM
You can find the build-out of the LB sandwich with TGW in our reference architecture. https://www.paloaltonetworks.com/resources/reference-architectures/aws As far as automation goes, we do have tag monitoring with DAG update capabilities native to the firewall in AWS. That will not solve your NAT Policy question though. Other customers typically build the firewall API calls into their CI/CD pipeline when the back end is built. An example of this flow can be found in our autoscale 2.0/2.1 templates. You can extract the PY code to incorporate it into your DevOps process. https://github.com/PaloAltoNetworks/aws-elb-autoscaling
... View more
LEGAL NOTICES
Copyright 2007 - 2022 - Palo Alto Networks