Lupasafe
Connect your customers' Lupasafe accounts so your product can read employee security-posture scores and device health data as part of onboarding or ongoing compliance monitoring. The customer pastes an API key and Askel handles the rest.
What you can do
Read employee security scores
Fetch per-employee posture scores that Lupasafe computes from device signals and behaviour data. Surface aggregate or per-user risk levels inside your product without duplicating the scoring logic.
List enrolled devices and their health status
Read device inventory including OS version, patch level, disk encryption status, and antivirus state for every device enrolled in the customer's Lupasafe account.
Fetch non-compliant employee records
Query employees whose posture score falls below the customer's defined threshold so your product can trigger remediation workflows or surface them in a risk dashboard.
Read policy violation events
Pull the event log of policy violations detected by Lupasafe, including timestamp, employee ID, and violation category. Useful for audit trails and compliance reporting inside your product.
Access department-level aggregates
Read security posture summaries grouped by department or team so your product can show management dashboards without exposing individual employee records unnecessarily.
Sync employee roster metadata
Read the list of employees enrolled in Lupasafe, including name, email, and department, to cross-reference with your product's own user directory during onboarding.
Enriching customer onboarding with employee risk signals
You sell a cyber insurance risk-scoring platform. A new customer, Cedarfield Group, has enrolled their 200-person workforce in Lupasafe. Your product needs to read their aggregate posture scores and identify employees with critical policy violations so you can produce an initial risk report at the start of the policy term.
- 1
Customer provides the API key
Cedarfield's IT manager opens the Lupasafe portal, navigates to Settings, copies the API key, and pastes it into your product's connection wizard. Askel validates the key with a test call to the Lupasafe API.
- 2
Employee roster sync
Askel reads the list of enrolled employees from Lupasafe and cross-references them with Cedarfield's user records in your product. Matched employees are linked to their Lupasafe profile ID for subsequent reads.
- 3
Posture score pull
Askel fetches posture scores for all 200 enrolled employees. Your product stores the scores and computes a company-level aggregate for the initial risk report.
- 4
Non-compliant employee list
Askel queries employees below Cedarfield's defined threshold (score below 60). Your product highlights 14 employees with critical violations: 8 with outdated OS versions and 6 with disk encryption disabled.
- 5
Risk report delivered
Your platform generates the initial risk report using the posture data and policy violation log from Lupasafe. Cedarfield's security lead sees the findings without anyone having to export a CSV from Lupasafe.
API token
The customer retrieves their API key from the Lupasafe portal under Settings. They paste it into Askel once. Askel sends it as an API key header on every request to portal.lupasafe.com; the key never reaches your servers.
How Askel sits between your product and the customer's system
FAQ for Lupasafe
Does Lupasafe require a specific plan to use the API?+
What happens if the customer revokes the API key?+
Can we read historical posture data, not just the current state?+
Is any personally identifiable information returned in posture data?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.