Support Case #1993 - Forge Industries Comply v2 Early Access Question

Sure, yeah. So, um, we've been on Aegis Comply for about eight months now and it's been really solid for us. But our compliance team — we report across multiple frameworks, we do SOC 2, we're getting into HIPAA because we've got a new healthcare adjacent part of the business, and then we have PCI requirements for some of our vendor payment processing. And right now, pulling reports for each of those is just... it's a lot of manual work.

Exactly. So we heard through, uh, I think it was a webinar or something, that there's a version two of Comply coming that has on-demand reporting across multiple frameworks. And we just — we really want to know if there's any way to get early access before the general release because our SOC 2 audit window is coming up and the timing would be really helpful.

Yeah so, um, I can share — and David correct me if I'm misstating anything here — but Comply v2 is essentially locked and going through final QA right now. The GA launch is actually scheduled for April 7th, so that's like, what, four days from now.

That's right, April 7th is the date we have, it's been on the roadmap for a little while and the team is feeling really good about it.

Full GA, available to all existing Comply customers. And the on-demand reporting piece — that's going to cover SOC 2, PCI DSS, HIPAA, and ISO 27001 right out of the gate. So your use case, Dana, honestly checks every box.

That's — okay, that's really exciting actually. Because we were almost starting to look at whether we needed a separate point solution just for the HIPAA piece and this would obviously be way cleaner to keep it all in one platform.

+2Dana says v2 is really exciting and avoids needing a separate HIPAA point solution. · product capability

Yeah absolutely, and that's kind of the whole vision behind v2 — consolidating that audit prep workflow so you're not bouncing between tools or doing a ton of manual exports. You essentially set up your framework mappings and then you can generate a report on demand whenever your auditor asks for it.

Can I ask a kind of dumb question — when you say on-demand, does that mean like, real-time? Or is there still some processing lag?

That's not a dumb question at all, it's actually a really common one. So the underlying data is continuously synced, so when you generate a report it's pulling from current state. There may be, you know, a minute or two of rendering time depending on the scope of what you're pulling, but it's not like a 24-hour batch job or anything like that.

And just to add to that — one of the things that came with v2 is also better evidence collection. So it's not just generating the summary report, it's actually attaching the relevant log references and control evidence inline, which is something auditors have been asking for.

Good question. So the v2 update will roll out automatically for existing customers, but there are a few configuration steps you'll want to do on your side to take full advantage of the multi-framework features. Specifically you'll need to go into the Comply settings and, um, map your existing controls to the new framework templates — v2 has a migration assistant for this that'll try to auto-map based on your current setup, but you'll want to review it.

Yes, there's going to be a full v2 migration guide published in the knowledge base on the 7th alongside the release, and we're also planning a customer webinar — David, what's the date on that?

I believe it's April 10th, a Thursday, I can send you both the invite after this call if that's helpful.

Please do, yeah. And actually can you send it to a couple people on my team? I've got two compliance analysts who are going to be the primary users on this.

Absolutely, just shoot me an email with their addresses and I'll get them added.

Perfect. Okay and — sorry, one more thing, this might be a little out of scope for this call but — we had been thinking about requesting some features around, um, custom control labeling within the reports. Like being able to tag controls with our internal policy numbers. Is that something v2 supports or is that more of a future roadmap item?

Ooh, that's a good one. So, um, v2 does have a custom metadata field option for controls — I don't want to overcommit on exactly how flexible it is but I believe you can add custom tags and labels. I'd want to double-check the specifics and follow up with you in writing so you know exactly what's supported.

And if it turns out there are gaps there, I'd love to formally log that as a feature request with the product team — that kind of internal policy cross-referencing is actually something I could see a lot of enterprise customers wanting.

Of course, glad we could help. I'll send over the webinar invite and follow up on the custom labeling question by end of week. Don't hesitate to reach back out through the case if anything else comes up before the 7th.