-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Lookout v3.0.1: Parser fixes, comprehensive and executive dashboards #13148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Fixed parser to properly handle device and app threat fields - Added comprehensive dashboard for detailed security monitoring - Added executive dashboard for high-level overview - Updated analytic rules with proper MITRE mappings - Enhanced data connector configuration - Updated to version 3.0.2
…columns, update version
|
@v-shukore please let me know if anything else is missing ? |
…finition - Added workbook2-name and workbook3-name to createUiDefinition.json outputs - Fixed ARM-TTK error: Parameters Without Default Must Exist In CreateUIDefinition - Updated Package/3.0.1.zip with the fix - Local ARM-TTK validation now passes all tests Amp-Thread-ID: https://ampcode.com/threads/T-51341ae4-51d0-4987-a64d-ffe634f19ba5 Co-authored-by: Amp <[email protected]>
Amp-Thread-ID: https://ampcode.com/threads/T-51341ae4-51d0-4987-a64d-ffe634f19ba5 Co-authored-by: Amp <[email protected]>
- Added all v2 API fields to LookoutEvents.json schema - Includes EventType, ThreatSeverity, DeviceGuid, and other v2 fields - Schema now matches parser output and analytic rule requirements - Fixes KQL validation errors for Lookout analytic rules Amp-Thread-ID: https://ampcode.com/threads/T-51341ae4-51d0-4987-a64d-ffe634f19ba5 Co-authored-by: Amp <[email protected]>
|
@v-shukore its failing on infoblox not lookout |
|
Hi @fgravato, we can ignore this check failure. Thank you! |
|
@v-shukore - is there anything else thats failing |
|
Hi @fgravato, to resolve this validation check please update your branch from master and commit. Thanks!! |
|
Hi @fgravato, could you add the workbookmetadata to the workbookmetadata.json file for the newly added workbooks, then repackage the solution and commit the changes? The location is provided below. |
…nd repackage solution Amp-Thread-ID: https://ampcode.com/threads/T-56c53083-3a23-4232-81ab-3ca955e9cf79 Co-authored-by: Amp <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR updates the Lookout solution to version 3.0.1, addressing Microsoft feedback from a previous PR with parser fixes, enhanced dashboards, and updated analytic rules with comprehensive v2 API field extraction.
- Parser enhancements to properly handle device and app threat fields with complete field extraction
- Four new workbooks added: Enhanced Security Dashboard, Executive Dashboard, IOA Investigation Dashboard, and Security Investigation Dashboard
- Four new V2 analytic rules with proper MITRE ATT&CK mobile tactics mappings (version 2.0.3) plus legacy rule update (1.0.1)
Reviewed changes
Copilot reviewed 69 out of 102 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| Workbooks/WorkbooksMetadata.json | Adds metadata for 4 new Lookout workbooks with proper data dependencies |
| Solutions/Lookout/validate_fixes.py | New validation script for analytic rules with MITRE mobile technique validation |
| Solutions/Lookout/Workbooks/*.json | Four new comprehensive workbooks for security monitoring and investigation |
| Solutions/Lookout/Validation/*.kql | New KQL validation queries for field coverage and health checks |
| Solutions/Lookout/Validation/*.md | Validation framework and results documentation |
| Solutions/Lookout/Workbooks/Images/ | Logo and preview images for workbook visualizations |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Solutions/Lookout/validate_fixes.py
Outdated
| if 'V2' in rule_name and conn_id != 'Lookout-Mobile-Threat-Defense': | ||
| errors.append(f"V2 rule should use 'Lookout-Mobile-Threat-Defense', found '{conn_id}'") |
Copilot
AI
Dec 1, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The line 53 has a hardcoded connector ID check 'Lookout-Mobile-Threat-Defense' that doesn't match the connector ID mentioned in the PR description. According to the validation report, all rules should use 'LookoutAPI' as the connector ID. This validation script appears to be checking for an incorrect connector ID value.
Solutions/Lookout/validate_fixes.py
Outdated
| @@ -0,0 +1,128 @@ | |||
| #!/usr/bin/env python3 | |||
Copilot
AI
Dec 1, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] Missing shebang execute permissions. The file has a shebang (#!/usr/bin/env python3) but should also have execute permissions set. While this doesn't affect functionality when called via python validate_fixes.py, it prevents direct execution as ./validate_fixes.py.
…ute permissions Amp-Thread-ID: https://ampcode.com/threads/T-56c53083-3a23-4232-81ab-3ca955e9cf79 Co-authored-by: Amp <[email protected]>
|
@v-shukore I have implemented the suggested changes:\n- Updated the connector ID check in |
|
Is there any updates on this ? |
|
Hi @fgravato, |
- Reverted changes to old ZIP files (1.1.0, 2.0.0, 3.0.0) - Removed internal development documentation (.md files) - Removed test/validation scripts (.py, .kql, .json dev files) - Keeping only 3.0.1.zip and necessary solution components Amp-Thread-ID: https://ampcode.com/threads/T-3060f9ae-4478-4c9d-861e-9134570ee4a5 Co-authored-by: Amp <[email protected]>
b649294 to
58cacb3
Compare
|
Hi @v-shukore, Thank you for the feedback! I've cleaned up the PR: Changes made:
Reason for the extra files: These were internal development artifacts (validation scripts, deployment guides, test data) that I used during development and testing. They were accidentally included in the PR and should not have been committed to the repository. I apologize for the oversight. The PR now contains only the necessary solution components for the 3.0.1 release. |
|
Hi @fgravato, thank you for your update. |
|
Hi @v-shukore, Thank you for the follow-up! Changes made:
The validation should pass now. Please let me know if anything else needs to be addressed. |
|
Hi @fgravato, as we have seen, the old packages are still appearing in this PR. Please remove those old packages from the PR; we only want the latest createui, maintemplate, and the latest zip included in package folder for this PR. Also, instead of deleting the old files, just uncommit those changes. |
|
@v-shukore Thank you for the feedback! I've reviewed the Package folder and confirmed that only the latest files are included in this PR:
The old packages (1.1.0.zip, 2.0.0.zip, 3.0.0.zip) exist in the repository from previous versions but have no modifications in this PR—they are unchanged. Please continue with the review when ready. Thanks! |
|
@v-shukore anything else ? |
|
no space left on device Thats on the pipeline end @v-shukore |
|
Hi @fgravato, we are working to resolve this issue and will merge the PR by tomorrow once it's done. Thanks!! |
|
Hi @fgravato, we checked and the URLs below are not working present in createui file on our end and are showing the error mentioned. If these URLs are working for you, could you please share a screenshot for reference? Otherwise, please replace them. https://enterprise.support.lookout.com/hc/articles/115002741773-Mobile-Risk-API-Guide Additionally, we would like to confirm whether the Thanks! |
- Removed enterprise.support.lookout.com links (require customer login) - Replaced with public URL: https://www.lookout.com/products/mobile-endpoint-security - Note and Important sections retained for Microsoft connector guidance Amp-Thread-ID: https://ampcode.com/threads/T-019b1406-f9cc-740b-9fe7-8bc98183778a Co-authored-by: Amp <[email protected]>
|
Hi @v-shukore, Thank you for the feedback. Regarding the broken URLs: The Regarding the Note and Important sections: Yes, these sections should remain in the createUiDefinition file. They contain important Microsoft-standard guidance:
These warnings help customers deploy the solution correctly and are aligned with Microsoft's connector migration guidance. Please let me know if you need any additional changes. |




Summary
Updates Lookout solution to v3.0.1 per Microsoft feedback with parser fixes and enhanced dashboards.
Changes Made (Per Microsoft Feedback)
Technical Changes
Testing
Files Changed
93 files (ONLY Lookout solution - no other solutions affected)
Related