A defined customer scope
Choose Active tenant data for the report you are preparing.
Build a security report around the customer's review, with branding set per template and data scoped to the tenant. Schedule delivery through the deployment's email service, or generate a file for your team to review, using the data available at generation time.
Choose the widgets for the customer review.
Set per template.
Reports read data at generation time.
Reports read data at generation time.
Required for subscription delivery.
Each sample report uses its own tenant context.
Choose MSSP from the report templates as the starting point for the customer review.
Use Active tenant data for Northstar and set branding per template.
Choose Weekly and PDF for E. Vos and T. Bakker. Subscriptions require the deployment email service.
History records generated reports. The customer examples use separate tenant scopes.
Start with a report template and choose the customer scope. Branding is set per template, so your reporting setup can reflect the audience as well as the security work you need to discuss.
Use the MSSP template as a starting point, then arrange the widgets your customer review needs in Report Builder. Set the report scope to Active tenant data for that customer and configure branding per template. A subscription carries the schedule and delivery format, so the reporting setup remains available for the next review instead of starting from a blank document each time. Before saving the schedule, check the customer scope and content with your team. The selected data is read when the report is generated.
Spend the review on what the records mean for the customer.
Illustrative customer and values. Not customer performance data.
Choose Active tenant data for the report you are preparing.
Keep the template and delivery schedule ready for the next review.
Use Reports in Settings to prepare the template and its subscription. Check the customer scope and generation setup before the report becomes part of your regular service review.
Choose a general or framework-specific template for the review.
Arrange widgets, choose the data scope and set branding per template.
Choose Daily, Weekly, Monthly or Custom (Cron), with the recipients and format.
Review generated reports and use the output for the customer discussion.
Reports read data at generation time. Subscriptions require the deployment's email service. PDF output requires a PDF renderer; generation can produce HTML when it is unavailable.
Casebook supplies the investigation context your team needs to explain an outcome. Core reporting organizes records for review, while The Portal keeps provider operations centered on the customer.
Reports are part of the core workspace. Check delivery configuration and permitted tenant scope.
Set the template, scope, branding and schedule once, and each customer's report is generated on time and delivered by email. Your team spends the review on what the records mean, not on assembling them.
Reuse the template and schedule instead of rebuilding the reporting setup.
Set tenant scope before generating the customer report.
Brand the template and keep the review organized around the customer.
Pick one customer and the security questions its report needs to address.
Check scope, branding and output before scheduling delivery.
Verify the email service and recipients, then save the subscription.
Yes. Use report templates and widgets to choose the content, select Active tenant data for the customer and configure the subscription schedule. Reports read data at generation time; cross-tenant reporting requires additional authorization.
Branding is set per report template. Review the branding configuration and license requirements with the Imperum team when planning your customer reports.
Report subscriptions require the deployment's email service. Choose Daily, Weekly, Monthly or Custom (Cron) and the delivery format. Reports support PDF, Excel or CSV; without a PDF renderer, generation can produce HTML.
Have any other questions? Talk to our team
Explore report templates, customer scope and delivery setup with the Imperum team.