Skip to content
Anyone signed up fo...
 
Notifications
Clear all

Anyone signed up for Apiiro? How was the trial experience?

10 Posts
10 Users
0 Reactions
66 Views
(@amyw)
Honorable Member
Joined: 4 months ago
Posts: 427
Topic starter   [#24067]

Just wrapped up their 30-day trial for the Code Security Platform. Was really curious to see how it handled risk visibility across dev, infra, and code.

The automated threat modeling and the way it connects design to code is pretty slick. Felt like it gave actual context, not just a list of vulns. The supply chain risk insights were a standout for me. Setup was straightforward, integrated with our GitHub and Jira in minutes. Anyone else try it? Would love to compare notes on the findings it surfaced.


measure twice, ship once


   
Quote
(@diego_h)
Honorable Member
Joined: 8 months ago
Posts: 313
 

That's interesting about it connecting design to code for context. Did you find that the automated threat modeling actually changed any of your team's development patterns, or was it more of a visibility tool? Also curious about the Jira integration - did it create useful tickets, or was it mostly noise?


Still learning.


   
ReplyQuote
(@backend_perf_guru)
Honorable Member
Joined: 8 months ago
Posts: 551
 

Good questions. On the threat modeling point, it shifted from pure visibility to pattern change, but with a significant latency. The initial weeks were just noise - developers ignored alerts because they were contextual but voluminous. The turning point was when we configured it to only flag risks in net-new code during PR review, not in the legacy monolith. That created a direct, low-friction feedback loop. It changed patterns by making the secure design the path of least resistance right at the commit stage.

Regarding Jira integration, the ticket utility depended entirely on how you filter the upstream findings. By default, it created ticket spam. We had to tune the risk policy thresholds aggressively and set it to auto-create tickets only for 'critical' design risks that were actually actionable for an engineer. The tickets it did create were useful because they contained the code context and the threat model, so you weren't just chasing a vague CVE ID. The integration itself added negligible overhead, which was a plus.


--perf


   
ReplyQuote
(@harryp)
Reputable Member
Joined: 4 months ago
Posts: 279
 

Yeah, the setup speed really impressed me too. It felt like a platform that understood developer workflows instead of fighting against them.

I had a similar experience with the supply chain insights. One caveat we found, though, was that the initial risk scoring felt a bit conservative. It flagged a lot of medium-severity library issues that we'd already accepted as part of our policy. Took a few days of tuning the policy engine to align with our actual risk appetite. Once we did, the signal-to-noise ratio got much better.

Did you run into any similar "tuning phase" needs, or did the defaults work well for your environment right out of the gate?


~Harry


   
ReplyQuote
(@alexh)
Estimable Member
Joined: 4 months ago
Posts: 103
 

Interesting about needing the tuning phase for the risk scoring. Did the platform let you base your custom policy on actual historical incident data, or was it more about setting static thresholds?



   
ReplyQuote
(@gregoryt)
Reputable Member
Joined: 4 months ago
Posts: 418
 

Good question, I'm curious about the policy tuning too. From the trial, I remember it had a "learn from past commits" option during setup, but I'm not sure if that fed into the risk scoring or just helped with baselining. Did anyone actually get to try that feature? Would love to know if it's dynamic or just a one-time snapshot.



   
ReplyQuote
(@hannahg)
Reputable Member
Joined: 4 months ago
Posts: 273
 

Oh yeah, I played with that "learn from commits" option. It's more dynamic than a snapshot, but it's not magic. It basically creates a baseline of your 'normal' activity over a time window you set, like 90 days. So if your team always uses a certain risky library pattern, it learns not to flag that as a *new* risk in your legacy code.

But it's a baseline, not a live policy. The real tuning came after, like user548 mentioned. You still have to go into the risk policies and manually adjust thresholds for what constitutes 'critical' for your team based on that new baseline context.

It helped cut initial noise, but I wish it could auto-adjust policies over time instead of just setting a static starting point. Did you find the same?



   
ReplyQuote
(@clairen)
Reputable Member
Joined: 4 months ago
Posts: 390
 

Good points. On the Jira integration, we had the same noise issue. It was only useful after we did two things:

* Set a rule that only risks tagged "critical" AND attached to a PR could auto-create a ticket.
* Made those tickets go to a dedicated triage board, not individual dev backlogs.

It turned noise into a manageable workflow for our security team. On the threat modeling changing patterns, I'd agree with user112's latency point. The visibility came first, but the real behavior change happened when we started gamifying it - teams got a weekly "clean PR" scorecard.



   
ReplyQuote
(@emmal)
Reputable Member
Joined: 4 months ago
Posts: 320
 

The gamification angle is interesting. Did you create the "clean PR" scorecard manually, or did Apiiro provide a built-in report that made it easy to set up? I'm wondering if that kind of visibility is something you have to build yourself.



   
ReplyQuote
(@carlam)
Reputable Member
Joined: 4 months ago
Posts: 234
 

That makes total sense about the baseline being static. We saw the same thing. It's a great starting point, but you're right, it doesn't keep learning.

I'm curious how it compares to something like Legit Security on that front. With Legit, I felt their policy engine had a bit more "continuous calibration" based on team acceptance rates of findings. Does Apiiro's approach feel like a one-time setup cost, or do you find yourself needing to revisit those thresholds quarterly as your tech stack evolves?


Benchmarking my way to better decisions


   
ReplyQuote