Superna Zero Trust - Partner Pack Submission

[Andrew-MacKay-CA]

Partner Pack Submission

Partner: Superna
Partner ID: Pending (awaiting XSOAR Alliances Team assignment)
Contact: support@superna.io
Website: https://www.superna.io

Pack Information

Name: Superna Zero Trust
Version: 1.0.10
Support Type: Partner

Description

Automate ransomware response with critical path snapshots and user NAS lockout/unlock via secure API integration.

What's Included

• Integration: SupernaZeroTrust

  • superna-zt-snapshot-critical-paths - Create snapshots of critical paths for rapid recovery
  • superna-zt-lockout-user - Lock out user from NAS storage during security events
  • superna-zt-unlock-user - Unlock user from NAS storage after threat resolution
  • Healthcheck endpoint for connection testing

• Playbooks: (4)

  • Superna Zero Trust Snapshot - Automated critical path snapshot creation
  • Superna Zero Trust User Lockout - Automated user lockout based on incident data
  • Superna Zero Trust Request User Storage Lockout - Manual user lockout with approval
  • Superna Zero Trust Request User Storage UnLockout - Manual user unlock with approval

Use Cases

• Ransomware incident response and containment
• Proactive threat containment during security investigations
• User access control during security events
• Employee termination and offboarding workflows
• Critical data protection and rapid recovery

Technical Details

• Python 3 integration
• RESTful API integration with Superna Zero Trust platform
• Secure API key authentication
• Support for both automated and manual approval workflows

Pre-Submission Checklist

• Validated with demisto-sdk validate
• Unit tests included
• Author_image.png included (120x50, <4KB)
• README.md documentation for pack and all components
• Professional logo (Superna branding)
• Healthcheck test endpoint implemented
• Demo video (will provide upon request)
• Cortex XSOAR Alliances Team approval (contacting: soar.alliances@paloaltonetworks.com)

Support

For questions or issues with this integration:

• Email: support@superna.io
• Website: https://www.superna.io

Notes

This is a Technology Partner submission. We are currently awaiting Partner ID assignment from the Cortex XSOAR Alliances Team. We will update this PR with the Partner ID once received.

relates: https://jira-dc-proxy.xdr.pan.local/browse/CIAC-15556

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Andrew-MacKay-CA
❌ Andrew

---

Andrew seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[content-bot]

Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @merit-maita will know the proposed changes are ready to be reviewed.
For your convenience, here is a link to the contributions SLAs document.

[content-bot]

Hi @Andrew-MacKay-CA, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link.

[samuelFain]

@Benimanela Kindly review the PR, thanks!

[content-bot]

For the Reviewer: Trigger build request has been accepted for this contribution PR.

[content-bot]

For the Reviewer: Successfully created a pipeline in GitLab with url: https://gitlab.xdr.pan.local/xdr/cortex-content/content/-/pipelines/6875394

[Andrew-MacKay-CA]

Hi @demisto/content-team,

The CI is failing due to two issues:

1. Missing docs-approved Label

The validation is failing because the docs-approved label has not been added. I've thoroughly reviewed all documentation in this PR:

✅ Integration README with detailed setup instructions
✅ Playbook READMEs for all 4 playbooks (Snapshot, Lockout, Unlock, Request flows)
✅ Pack README with use cases and configuration
✅ Release notes for all versions (1.0.1 through 1.0.13)
✅ Enhanced HTTP 429 error handling documentation

Could a maintainer please review the documentation and add the docs-approved label if it meets standards?

2. CLA Signature Status

I have signed the Contributor License Agreement, but the CLA check is not showing as passed. Could you please verify my CLA signature status?

Signed with:

• GitHub Username: Andrew-MacKay-CA
• Email: andrew.mackay@superna.net

Thank you for your assistance!

Andrew MacKay
Superna

[Andrew-MacKay-CA]

Additional Check Failures

I see there are 3 additional required checks failing:

1. Partner-Approved Label (REQUIRED)

This pack is a partner contribution from Superna. Could the maintainers please:

• Add the Partner-Approved label to this PR
• Or direct me to the proper contact at Palo Alto Networks Alliances Team for partner approval

I will also email soar.alliances@paloaltonetworks.com to request Partner ID and approval.

2. Pre-commit Validation

The pre-commit check is failing. Could a maintainer please provide details on:

• What specific validation errors are causing the failure?
• Are the BA101 warnings (playbook name/ID mismatch) the cause? These were present during initial validation and are typically force-mergeable.

3. CLA Signature

As mentioned in my previous comment, I have signed the CLA but it shows as "pending". The CLA assistant URL is: https://cla-assistant.io/demisto/content?pullRequest=42690

Could you please verify my signature status?

---

Summary of blockers:

• ✅ Code ready and tested
• ⏳ Awaiting docs-approved label
• ⏳ Awaiting Partner-Approved label
• ⏳ Awaiting CLA verification
• ⏳ Need details on pre-commit failures

Thank you for your assistance!

[Andrew-MacKay-CA]

Partner ID Added ✅

I have received my Partner ID from the Palo Alto Networks Alliances Team and updated the pack metadata.

Partner ID: 2989092

Changes:

• Updated pack_metadata.json with "partnerId": "2989092"
• Commit: 51190dc

This should resolve the Partner-Approved label requirement. Could the maintainers please:

1. Verify the Partner ID is correct
2. Add the Partner-Approved label to this PR

Thank you!

[Andrew-MacKay-CA]

I have signed the CLA several times but shows required still, please confirm it's signed.

[Benimanela]

Hi @Andrew-MacKay-CA, Thank you for the work on this contribution. The implementation looks good overall, but there are several issues that need to be addressed before moving forward.

General

• Please align the pack file structure with XSOAR standards, as described here:
  https://xsoar.pan.dev/docs/packs/packs-format
  There are currently several unnecessary files in the pack.
• If this is a new pack, please set the pack version to 1.0.0 and remove the release notes.
• Please run demisto-sdk format on all pack files.
• Please run demisto-sdk validate and ensure it passes successfully.

Playbooks

• Please add playbook screenshots to the doc_files folder.
• Please add an initial step in all playbooks to check whether the Superna integration exists and is enabled.

Superna Zero Trust Snapshot Critical Paths

• Please clarify the playbook use case in the documentation.
• The playbook defines username as an input, but this input is not used anywhere in the playbook. Please either use it or remove it.

Superna Zero Trust User Lockout

• In step 5, the playbook prints ${inputs.apiurl} and ${inputs.username}.
• ${inputs.apiurl} is not defined in the playbook inputs. Please either define it properly or remove its usage.

Let me know once the fixes are in place so I can take another look.

[Andrew-MacKay-CA]

Hi Benimanela

This PR should address remaining items 2fe2981

[Benimanela]

Hi Benimanela

This PR should address remaining items 2fe2981

Looks good! Please also fix this.

Playbooks:

Please add an initial step in all playbooks to check if the Superna integration exists and is enabled.

[Andrew-MacKay-CA]

Hi Benimanela,

I pushed 4 updated playbooks, can you let me know remaining steps.

[Benimanela]

Approved from my end.
Please replace the screenshot of the playbook with the updated version.

[Andrew-MacKay-CA]

Hi Benimanela,

Updated with screenshots, what are the next steps?