Arnica AppSec Core Enterprise Platform

What do you like best about the product?

Works well within existing pipelines. The dashboards are intuitive to use. It's is simple for developers to find their findings to address their code issues.
The SLAs per branch is useful when you have many different
development teams. The newer AI capabilities work well to find real issues instead of FUD.

What do you dislike about the product?

While the dashboard is intuitive, management reporting would be useful. The lack of DAST compared to competitors is a small issue.

What problems is the product solving and how is that benefiting you?

We can find and resolve coding issues earlier in the SDLC, reducing the cost to fix problems which speaks to the ROI of the product.

What do you like best about the product?

I deployed Arnica to replace Checkmarx at a previous company, and I have brought it with me to several startups I support since then. I still use it in my current role, in a somewhat different capacity than the full enterprise program I originally ran.

The policy engine was the primary reason we selected it after evaluating multiple products, since none of the other vendors we tested could offer comparable granularity at the time. It deployed fast across GitHub and Azure DevOps through SCM integration, with no CI rework to start getting value, and our first blocking policy was live within 90 days.

We were able to create granular PR policies on severity, EPSS, finding type, direct versus transitive and prod versus dev dependencies, and package reputation, which let us stage enforcement from annotations into blocking and turn rollout into measurable maturity milestones.

It also strengthened our Security Champions program, since we could empower champions to review dismissals for their own teams. Developer experience improved because people handled findings in code they were already changing instead of years of historical debt.

Customer success has been a genuine strength, responsive and willing to help with rollout, and several requests we raised shipped faster than I expected.

The SBOM explorer experience is also something I personally appreciate, I use it regularly to check exposure across the organizations I support whenever another large supply chain attack hits the news.

My use of the AI review features is still early, more proof of concept than a rollout. I feel positive about the direction, since reviewing AI-generated code is a real challenge and having policy enforcement meet it at the source is the right place to solve it.

On cost, it was priced competitively against the other vendors we evaluated and the per-identity model scaled sensibly as the team grew.

What do you dislike about the product?

Dashboard and reporting could be smoother, especially for executive or audit reporting, though I did not find it better in Checkmarx, Snyk, or GitHub Advanced Security. The API was accessible and well-documented enough that our vulnerability management aggregation platform built an integration to it, and we separately pulled findings into our own reporting.

We had some early challenges with SAST rule quality for older, non-web languages, C++ in particular, where SAST quality tends to be inconsistent industry-wide. We worked with Arnica on custom rules and coverage has improved since.

No DAST, which was a lower priority given our focus on pre-production risk, but runtime-heavy teams should weigh that.

The per-identity pricing model also made direct comparison against other vendors trickier, since most of them price differently, and it took some work to walk our finance stakeholders through it before a deal could move forward, though we concluded the pricing was fair once we normalized the comparison.

What problems is the product solving and how is that benefiting you?

The goal was to get more traction from existing application security coverage across SCA, SAST, secrets detection, and SBOM, without slowing engineering down on GitHub and Azure DevOps. In a previous deployment we selected it because we were not seeing consistent, organization-wide reduction in findings, largely because of how findings were delivered, and we wanted a tool that would let us run a focused, prioritized reduction process.

Delivering findings at the SCM layer meant developers mostly dealt with issues in the code they were actively changing rather than a backlog of historical debt they had no context for, which is what finally moved the needle on reduction.

The policy engine flexibility gave us a concrete way to prioritize in a common way across our other product security programs, since we could place emphasis on issues with demonstrated impact that came through bug bounty and red team work, and further tie that back to how Security Champions reviewed and drove remediation on their teams. That pulled four programs into a shared product security effort with a common incentive.

The other ongoing benefit is supply-chain visibility, when a major dependency compromise hits the news, I can check exposure across the organizations I support quickly.

What do you like best about the product?

ou quickly understand the security posture of your codebase and can maintain continuous oversight while delegating day-to-day security responsibilities to contributing developers.

What do you dislike about the product?

The user interface can be confusing. For example, I couldn't easily find the option to remove a monitored repository.

What problems is the product solving and how is that benefiting you?

Nowadays, as hybrid code developed by both humans and AI agents is rapidly created and deployed, security risks are increasing exponentially. I needed a budget-sensitive tool that could help me mitigate those risks.

What do you like best about the product?

Easy setup and administration was my favorite part. It had what we needed, but took a fraction of the time to set up.

What do you dislike about the product?

It can be tedious logging in multiple times throughout the day, but Short login sessions are generally more secure.

What problems is the product solving and how is that benefiting you?

Arnica assists us with vulnerability detection (SAST and SCA), and it's prioritization to make meaningful strides in remediation.

What do you like best about the product?

Development and Security are often at odds when granting elevated privileges to source code repositories. A security team asking developers to prove they need elevated privileges causes the "Trust Me" conversation, where developers argue that they should be trusted to have complete control of the source code.

Adopting Zero Trust strategies is helping to remediate over-provisioning in many systems, but source code repositories remain a source of contention. Arnica allows Security teams to discover elevated privileges that have been granted but rarely if ever, used.

With Arnica, Need to Know & Least-Privileged Access metrics are always available without input from developers.

Removing unused, elevated privileges effectively reduces the attack surface and associated risk to intellectual property.

Remediation of discovered overprovisioning is simple and easily documented for change control.

What do you dislike about the product?

The complete feature set in Arnica is only available to GitHub Enterprise organizations. Smaller teams not ready to move to GitHub enterprise will not have the full set of protections.

However, discovering and mitigating risk in source code repositories at any level improves overall risk in any software firm.

What problems is the product solving and how is that benefiting you?

Securing source code in Agle software firms requires visibility into the privileges granted to the Organization. Repositories are often misclassified as public or "open source" when the proprietary nature of the project is not fully understood. Individuals with unnecessary elevated privileges can expose intellectual property by facilitating collaboration inappropriately.

Arnica gives firms visibility, analysis, reporting and remediation capabilities on GitHub. Securing the organization without removing privileges that are necessary for the appropriate individuals.

What do you like best about the product?

Could not be easier to use. Quickly connect to your GitHub and get a robust delineation of all potential vulnerabilities in your repository. Can't wait for more features to come out and to use this tool more regularly as our team scales.

What do you dislike about the product?

Very limited areas of confusing UI and ideally would love to see more integrations across my stack to detect vulnerabilities and excessive perms.

What problems is the product solving and how is that benefiting you?

Peace of mind knowing that our repo is safe and tightly controlled with a revolving door of contractors coming in and out of our operation.

What do you like best about the product?

Arnica's detections are data-driven, which means it is most likely a true positive when something is detected.
Taking action with Arnica against its detection helps ease the mitigation process.
Arnica's team is always looking to expand its discoveries with new types of detections and improve existing ones.

What do you dislike about the product?

We look forward to expanding our use of Arnica in our environment.

What problems is the product solving and how is that benefiting you?

Arnicas solves the Git access management problems that are always left behind because it is time-consuming and hard to manage.
The fact that it is done automatically with intelligence helps us implement the solution and take action confidently.

What do you like best about the product?

With Arnica, we are streamlining the review process through data driven analytics and automation to guard against the accumulation of excessive permissions. Arnica has already paid for itself through process optimization and developer tool cost savings by right sizing commercial license.

What do you dislike about the product?

We are happy with the product capabilities. We are eager to see how the feature set grows.

What problems is the product solving and how is that benefiting you?

We are securing the devops supply chain. We are also managing entitlements and permissions for our 3000 developers. The tool is also being used to manage down waste in licensing unused tools.