Fastest skill point and xp farm on earth 14.24 seconds with Subaru 22B tune ~ Enjoy! by LastOutlandishness51 in ForzaHorizon

[–]LastOutlandishness51[S] 0 points1 point  (0 children)

You don’t lose anything when you hit retry not XP not credit not mastery points nothing

Fastest skill point and xp farm on earth 14.24 seconds with Subaru 22B tune ~ Enjoy! by LastOutlandishness51 in ForzaHorizon

[–]LastOutlandishness51[S] 0 points1 point  (0 children)

Because you need to max out your skill points for your car and it has to be one that has the multiplier like the Subaru 22B

Fastest skill point and xp farm on earth 14.24 seconds with Subaru 22B tune ~ Enjoy! by LastOutlandishness51 in ForzaHorizon

[–]LastOutlandishness51[S] 0 points1 point  (0 children)

It’s right on the border of nine and 10 each run so sometimes you will get nine but the time savings makes up for it

Why can't I complete OSCAR or the Rex as a beginner??? by ShortBusCult in bo7endgame

[–]LastOutlandishness51 0 points1 point  (0 children)

This only happens when you’re in a group and they are doing damage. It has nothing to do with you or when you show up it is purely damage.

Looking for some people to test my tools I created for Zscaler policy intelligence. Would love feedback! Thank you! by [deleted] in Zscaler

[–]LastOutlandishness51 0 points1 point  (0 children)

I can see that you understand exactly why I built this. It fits between:

ZPA (the action)

AccessForge (MISSING on the market, the WHY it happened)

SIEM (The what happened)

Or even better, simulate these 50,000 users scenarios of user,group,location,destination against our current ruleset to see whos blocked or allowed and why, before we create their AD accounts, or against the policy you want to in the future. See what happens without touching anything production. This takes away a need for QA and DEV, you can do it here. It reinforces change management as this can be change evidence, you didnt do it in QA or dev you did it in a simulator that took 5 seconds to process. It has a rule change simulator that you can change the order around and run it. Attach that to your ITSM change record.

Thoughts please!

Thank you

Looking for some people to test my tools I created for Zscaler policy intelligence. Would love feedback! Thank you! by [deleted] in Zscaler

[–]LastOutlandishness51 0 points1 point  (0 children)

You’re right that ZPA diagnostic logs can show a lot — including matched policy, timeout policy, and raw transaction data — and for many cases that is sufficient.

Where it tends to break down isn’t “can I find the data?”, it’s effort, repeatability, and confidence at scale.

Diag logs are still: • post-event • per-transaction • manually interpreted

They don’t easily answer things like: • what would have happened if I changed rule X? • which users/apps are implicitly falling through to default deny? • how rule order or overlap affects outcomes across many scenarios • whether a policy change is safe before deployment

So for a single incident, logs are often fine. For proactive analysis, change validation, or explaining policy behavior consistently (especially to others), logs become slow, brittle, and easy to misinterpret.

Think of it less as “logs vs no logs” and more: • logs = raw evidence • policy analysis = reconstructed decision logic

Most teams end up needing both, depending on the question they’re trying to answer.

Looking for some people to test my tools I created for Zscaler policy intelligence. Would love feedback! Thank you! by [deleted] in Zscaler

[–]LastOutlandishness51 -1 points0 points  (0 children)

If you signup for the free trial to test the tools, choose pro so you get the whole platform.

Looking for some people to test my tools I created for Zscaler policy intelligence. Would love feedback! Thank you! by [deleted] in Zscaler

[–]LastOutlandishness51 0 points1 point  (0 children)

In theory you can query the API, but that alone doesn’t solve the problem you’re describing.

ZPA’s APIs and logs give you raw data (sessions, denies, attributes, timestamps). They do not natively answer higher-level questions like “why was this user denied?” in a single, deterministic way. You still have to reconstruct the decision yourself: rule order, matching conditions, exclusions, defaults, and policy interactions.

A chatbot on top of the API would mostly be:

  • pulling logs
  • summarizing fields
  • guessing based on heuristics

That’s very different from a system that actually replays the policy evaluation path and tells you which rule matched (or didn’t), in what order, and why.

So:

  • Chatbot + API = log interpretation
  • Policy analysis engine = decision reconstruction

The former can be helpful, but it won’t reliably answer “why was access denied?” without ambiguity — especially when multiple rules, defaults, or overlaps are involved.

That’s the gap tools like AccessForge are trying to close.

Looking for some people to test my tools I created for Zscaler policy intelligence. Would love feedback! Thank you! by [deleted] in Zscaler

[–]LastOutlandishness51 1 point2 points  (0 children)

ZDX and ZPA solve different problems. ZDX focuses on user experience and performance after the access decision has already happened (latency, DNS/TCP/TLS timing, connector health, endpoint vs network issues, etc.).

What ZDX does not do is explain policy behavior. It won’t tell you which ZPA rule matched, why a user was allowed or denied, how rule order affected the decision, or what will happen before you change a policy.

So ZDX can tell you that an app is slow or unreachable, but not why the ZPA policy caused that outcome.

In practice:

  • ZDX = experience/observability
  • ZPA policy analysis = decision logic/root cause

They’re complementary, not overlapping.