LogoLogo
Log In
  • Introduction
  • Registration
  • Pre-Requirements & Initialization of the Platform
    • Agent Installations
      • Windows Installation
      • Linux Installation
      • macOS Installation
      • Deploying Agent From Microsoft Intune
    • Access and Exlusion Requirements
      • Agent-Based Demo Deployment
      • Agent-Based Production Deployment
      • Agent-Based On-Premises Deployment
      • Trendmicro Exlusions
    • Troubleshooting
  • Getting Started
    • Platform Overview
    • Agent Based Deployment
      • 1. Activating Policies
      • 2. Configure Policies in the Group
      • 3. Agent Deployment
        • Windows: Downloading and Deploying The Windows Agent
        • Linux: Downloading and Deploying The Linux Agent
        • macOS: Downloading and Deploying The macOSAgent
      • 4. Enabling Classification Rules
      • 5. Review The Results & White Listing
      • 6. Reviewing and Enabling Sigma Rules
      • 7. Generating Reports
      • 8. Notification Settings
      • 9. YARA Analysis & THOR
      • 10. Configuring YARA Rules
      • 11. Remediation Management
      • 12. Results of The Analysis
    • Using the Main Dashboard and Grids
    • Classification Rules
    • Configuring Modules
      • Threat Hunting
        • Enabling Windows Autoruns & Process Analysis
        • Enabling Weak SNMP Discovery
        • Enabling Linux Analysis
        • Job Management
        • Customizing Classification Rules
        • Enabling Windows Event Log Analysis
        • Enabling Windows Sysmon Analysis
        • Enabling Windows Thor Analysis
        • Enabling Windows Security Benchmark Analysis
        • Enabling In-Depth Analysis
      • Windows Hardening
      • Remediation & Response Management
      • Notification Management
      • Vulnerability Management
      • Network Discovery
      • Windows Patch Management
      • IP Scanning
      • Software Management
      • Managing Shadow-IT
      • Microsoft Windows Defender Health Analysis
    • Configuring Sysmon
      • Sysmon Deployment
      • Managing Sysmon Rules
      • Troubleshooting Sysmon Rules
    • Important Settings
      • Organization Settings
    • Utilizing the Platform Effectively and Interpreting the Artifact Analysis Results
    • How To Manage False Positives and Optimizing the System
    • Using AI Modules
      • AI Manuel Enrichment
      • AI Auto Enrichment
      • Automating AI Enrichment
      • AI Auto Exclusions
      • AI Feedback Questions
      • AI Auto Exclusion & Enrichment for Sysmon
      • AI Activity Logs
    • GRC Management
      • Creating an Assessment & Updating Evidences
    • Integrations
      • Office 365 Azure Registration
      • Windows Security Center Azure Registration
      • Azure Active Directory Integration
      • Active Directory Integration
      • CrowdStrike Integration
      • Palo Alto - Cortex Integration
      • Palo Alto HyperVisor Integration
      • OpenVAS Integration
      • Tenable Nessus
      • Gophish Integration
      • Prowler Integration
    • How to Use CyberCyte Platform Effectively?
    • Enabling External Exposure Analysis
  • Administration Guide
    • Most Used
      • Threat Overview
      • Analysis & Investigation
      • Shadow IT
      • My Assignments
      • Installation Management
      • Policy Management
      • Windows Hardening Results
      • Device Management
    • Dashboards
      • Threat Overview
      • Asset Overview
      • User Overview
      • Shadow IT
      • Analysis
    • Threat Hunting
      • Notable Events
      • Analysis & Investigation
      • Visualization
      • Hunting Settings
      • E-Mail/Teams Settings
    • Threat Response
      • Response Management
      • Incident /Case Management
      • ToDo
      • Remediation & Response Settings
      • Incident /Case Management
      • Incident/Case Management Settings
      • AI Activity
      • Interactive Sessions
    • Security Assurance
      • Hardening & Configuration Management
      • Vulnerability Management
      • Windows Remediation
      • Linux Remediation
      • Software Management
      • Windows Patch Management
      • Windows Remediation & Response Settings
      • Hardening & Configuration Management Settings
    • Asset Management
      • Endpoint Management
      • Group Management
      • Settings
    • Rules & Policies
      • Artifact Classification
      • Policy Management
      • SIGMA/YARA Rules
      • Artifact Collection Parameters
    • GRC
      • Assessment Management
      • Risk and Oppurtunity Management
      • Incident/Case Management
      • Assets
      • Document Management
      • Evidences
      • ToDo & Project Management
      • Parameters
      • Settings
      • Incident/Case Management Settings
    • Settings & Reporting
      • Agents Settings
      • Deployment Settings
      • Notification Settings
      • Integration Settings
      • AI Settings
      • Credential Settings
      • Organization Settings
      • Reporting
      • Users & Groups
    • Help
      • Ask AI
      • Configuration Wizard
      • Help Guide
      • Search
      • Version & Exception Overviews
      • Troubleshoot
    • How To Manage False Positives and Optimizing the System
  • Troubleshooting
    • Troubleshooting Multitenant Functionalities & Accessing Internal Applications
    • The Agent Troubleshooting
      • Troubleshooting the Windows Agent
      • Troubleshooting the Linux Agent
      • Troubleshooting the macOS Agent
    • Proxy Troubleshooting
      • Portal Server
      • Elastic Server
    • AI Automation Troubleshooting
      • Checking the AI Mode
      • Checking AI Audit Logs
      • Checking the AI Settings
    • Troubleshooting Synchronization Problems
  • Release Notes
    • v3.3.6
    • v3.3.5
    • v3.3.4
    • v3.3.3
    • v3.3.2
    • v3.3.1
    • v3.3
    • v3.2.1
    • v3.2
    • v3.1.4
    • v3.1.3
    • v3.1.2
    • v3.1.1
    • v3.1
    • v3.0.10
    • v3.0.8-9
    • v3.0.7
    • v3.0.6
    • v3.0.5
    • v3.0.4
    • v3.0.3
    • v3.0.2
    • v3.0.1
    • v3.0
    • v2.5.0 - v2.17.7
Powered by GitBook
On this page
  • 1. Triggering the Background Job
  • 2. Setting Up The Linux Server and Scanner Component
  • 3. Connection Configurations
  • Amazon Web Services (AWS):
  • Microsoft Azure:
  • 4. Creating a Policy For Integration
  • 5. Checking The Results

Was this helpful?

  1. Getting Started
  2. Integrations

Prowler Integration

PreviousGophish IntegrationNextHow to Use CyberCyte Platform Effectively?

Last updated 5 days ago

Was this helpful?

The CyberCyte portal can integrate with Gophish for further analysis and investigations. To integrate, please follow these steps:

1. Triggering the Background Job

Navigate to "MSSP“ -> "SUPERORG Management", it will automaticly trigger the background job.

2. Setting Up The Linux Server and Scanner Component

  1. Login to the Linux server for deployment of the cloud scanner component. Please use SFTP for uploading the component to the server (CyberCyte will prove the scanner component). Execute these comments below on the Linux server:

  • chmod +x /tmp/CyberCyteCloudExposureScanner-<version>

  • mv CyberCyteCloudExposureScanner-<version> CyberCyteCloudExposureScanner

  • /tmp/CyberCyteCloudExposureScanner --setup

This commands for inital deployment. For the upgrade please execute these commands:

  • chmod +x /tmp/CyberCyteCloudExposureScanner-<version>

  • mv CyberCyteCloudExposureScanner-<version> CyberCyteCloudExposureScanner

  • /tmp/CyberCyteCloudExposureScanner --update

  1. After initial setup please configure settings.json with these values below:

{ "concurrent_orgs": 5, -> How many org that can be handled at the same time, "endpoint_url": "" -> The portal address }

  1. Start the service after the configuration with these command below:

  • ./CyberCyteCloudExposureScanner --install-service

After the starting the service it should be appear under the “/#/console/cloud_exposure_scanner_settings”.

3. Connection Configurations

To create a credential for AWS or Azure Cloud services used in the infrastructure, we need to follow the steps below:

Amazon Web Services (AWS):

Microsoft Azure:

  1. Login to the Azure portal and navigate to “App Registrations” and create an app with “Single Tenant” with no URL.

  2. On the created app, configure API permissions with permiting these values below:

Directory.Read.All

Policy.Read.All

UserAuthenticationMethod.Read.All (optional, for MFA checks)

  1. Save and grant the permissions.

  2. Navigate “Certificates & Secrets” and click on the “Add Client Secret” inside of the app. This action will create an new secret. The “Value” is client secret and under the “Overview” section there is “Tenant ID” and “Subscription ID”. Save these values, we will use that values in the next steps.

  1. Take some of the role form Prowler’s official repository and save it as a json file:

  1. Configure json files values like this:

"assignableScopes": [ "/subscriptions/<SUBSCRIPTION ID>" ],

  1. After configuration, please navigate to Azure portal again, under the “Subscription” → “IAM” click on “+Add” button and save .json file as a custom role. After adding the custom role, click on the “+ Add Role Assignment” and assign this role as a applicaiton member.

  1. Back to the CyberCyte portal and create a credential with selecting “Graph API”.

4. Creating a Policy For Integration

For creating a policy select "Scenario/Discovery/Integration" -> "Cloud Configuration”. Select the credential, the group assignment is not important.

5. Checking The Results

We can observe the results under the “Security Assurance”: “/#/security_assurance/cloud_configuration_management/security_controls_prowler_results”

Please login to the AWS portal and navigate to “AIM” → “My Security Credentails” (). Under the “Access Keys” we need to create an access key and secret key, then take these values to the CyberCyte portal.

https://xxx.yyy.com
https://us-east-1.console.aws.amazon.com/iam/home?region=eu-north-1#/security_credentials
prowler/permissions/prowler-azure-custom-role.json at master · prowler-cloud/prowler