How to configure Ryver

To configure Ryver, you need to set up both your user preferences and, if you are an admin, manage team, forum, and integration settings. Ryver is largely cloud-based, so most configuration is done from within its web or desktop app.

Basic User Configuration:

  • Go to the “My Settings” section by clicking your user avatar or the “^” icon at the bottom of the navbar.

  • In “My Settings”, you can:

    • Change notification preferences (e.g., enable/disable email notifications).

    • Set your display name, profile picture, and contact details.

    • Adjust language, timezone, and interface settings.

Team and Forum Setup (Admins):

  • Create Teams and Forums to structure your organization’s communication:

    • Teams: Smaller, focused groups for private discussions and task management.

    • Forums: Organization-wide spaces for open communication with selected guests.

  • In the left sidebar, click “Teams” or “Forums” to add or manage them.

Task and Communication Management:

  • Use chat for group or private conversations.

  • Use “Topics” inside forums and teams for focused threaded discussions.

  • Use the task manager to assign or track tasks; you can turn any conversation into a task.

Integrations:

  • Ryver supports integration with other tools via Zapier, Make, or Boost.space for automating workflows (e.g., connecting email, file storage, or project management apps).

  • To set up an integration, follow the third-party service’s connection process (e.g., enter your Ryver subdomain, admin credentials, and grant API permissions as needed).

News/Alert (Watches):

  • Set up Watches to monitor keywords, RSS feeds, or social media mentions; these alerts can post directly into a designated Team or Forum.

Tips:

  • You may pin your favorite Teams, Forums, and People for quick access.

  • Adjust notification settings under “My Settings” to manage alerts and reduce email volume.

  • Ryver apps are available for Windows, Mac, iOS, and Android for easy access anywhere.

[mai mult...]

How to configure Redmine

To configure Redmine, you need to follow a series of steps that involve installing dependencies, setting up the database, configuring the application, and preparing your web server. These steps are similar across most installations, whether you use Ubuntu or another supported platform.

Basic Redmine Configuration Steps:

  1. Install Required Dependencies

    • Install necessary packages such as Ruby, Rails, a web server (Apache or Nginx with Passenger), and a database (MySQL, MariaDB, or PostgreSQL).

  2. Install Redmine

    • You can install Redmine from the package manager or download it from the official website.

  3. Set Up the Database

    • Create a new database and database user for Redmine. Grant the required permissions.

  4. Configure the Database Connection

    • Copy the sample database configuration file and edit it with your database credentials:

      text
      cp config/database.yml.example config/database.yml
      nano config/database.yml

      Fill in the username, password, and database name you created.

  5. Generate a Secret Token

    • This is necessary for session security:

      text
      bundle exec rake generate_secret_token
  6. Create the Database Schema

    • Initialize the Redmine database with the required tables:

      text
      RAILS_ENV=production bundle exec rake db:migrate
      • On Windows:

        text
        set RAILS_ENV=production bundle exec rake db:migrate
  7. Load Default Data (Optional but Recommended)

    • This step populates the database with default configuration data, including languages:

      text
      RAILS_ENV=production bundle exec rake redmine:load_default_data
  8. Set File System Permissions

    • Ensure the web server or Redmine user owns and can write to the necessary directories like fileslogtmp, and relevant asset directories.

  9. Configure Your Web Server

    • For Apache:

      • Edit Apache config files, set up Passenger, and create needed symlinks.

      • Restart the web server after changes:

        text
        sudo service apache2 restart
  10. Start Redmine

    • Start the application server (e.g., Puma or Passenger). Verify access via a web browser.

  11. Log In as Administrator

    • Default credentials are usually:

      • Username: admin

      • Password: admin

    • Change the password after the first login.

  12. Adjust Redmine Settings

    • Go to Administration > Settings in the web interface to customize notification, email, attachment, issue tracking, and integration settings.

[mai mult...]

Properly use and manage networks in Google Admin Center

To properly use and manage networks in Google Admin Center (Admin Console), follow these best practices and steps:

1. Setting Up and Managing Network Configurations

  • Sign in to the Admin Console with an administrator account

  • Navigate to Devices or the relevant section for managed devices

  • Select the organizational unit (OU) if you want to apply network settings to a specific group (like a department or team).

  • To add a network:

    • For Wi-Fi, Ethernet, or VPN: Click to create the desired network type (e.g., “Create Wi-Fi network” or “Create VPN network”).

    • Enter the required details such as network name, authentication method (e.g., WPA2-Enterprise for Wi-Fi, 802.1X for Ethernet), or VPN configuration (remote host, VPN type, credentials).

    • Specify which device platforms (ChromeOS, Android, iOS, etc.) can use this network.

    • Optionally, set the network to connect automatically for managed devices.

  • To edit or remove a network, select the existing configuration, make changes, and save, or click “Remove” to delete it from the OU.

2. Best Practices for Network Management

  • Use organizational units to apply different network policies to different groups.

  • For Wi-Fi and Ethernet, prefer secure authentication (such as 802.1X Enterprise) to protect network access.

  • For VPN, ensure only supported configurations are pushed, and use strong credentials and certificates1.

  • Regularly review and update network configurations as your organization’s needs change.

3. Advanced Network Design and Connectivity (Google Cloud)

If your organization uses Google Cloud networking (VPCs, hybrid networks, etc.), consider these best practices:

  • Choose the right VPC connection method for your needs (Network Connectivity Center, VPC Peering, Cloud VPN, etc.).

  • Use Cloud NAT for fixed outbound IPs and secure internet access for VMs without external IPs.

  • Use private DNS zones for internal service name resolution.

  • For Google API access, use Private Google Access or Private Service Connect to allow secure, internal API communication without public IPs.

  • When managing complex network topologies (multiple VPCs, hybrid cloud), use Network Connectivity Center and assign appropriate IAM roles (like Network Management Admin or Hub Admin) to control who can create, modify, and review network connections and routing.

4. Permissions and Roles

  • Assign Network Management Admin or Network Management Viewer roles as appropriate to control access to network management features and resources.

  • For VPC hub and spoke architectures, use the Hub Admin role to manage connectivity and routing between networks.

[mai mult...]

How to efficiently manage mobile devices and endpoints in Google Admin Center

To efficiently manage mobile devices and endpoints in the Google Admin Center (Admin Console), follow these structured steps:

1. Access the Admin Console

  • Log in at admin.google.com using an administrator account

2. Navigate to Device Management

  • Go to Devices in the left-hand menu

  • Select Mobile & endpoints to manage both mobile devices and other endpoints (such as laptops and desktops)

3. Choose the Appropriate Management Level

  • Basic Management: Provides core security features like password enforcement and account wipe. No device agent installation is required and is enabled by default.

  • Advanced Management: Offers enhanced controls, including app management, device settings enforcement, remote wipe, and detailed reporting. Requires device policy app installation for Android/iOS and an Apple Push Certificate for iOS devices.

  • Custom Management: Allows you to apply different management levels (unmanaged, basic, advanced) for different device types or organizational units.

To enable or adjust management:

  • Go to Devices > Mobile & endpoints > Settings > Universal.

  • Select your organizational unit if you want to apply settings to a specific group.

  • Choose BasicAdvanced, or Custom management, then click Save.

4. Set Up Device Policies and Security Controls

  • Enforce passcodes, screen locks, and device encryption

  • Set up device approvals to control which devices can access corporate data

  • Configure remote actions such as lock, wipe, or block for lost or non-compliant devices

  • Manage apps (approve, block, or push apps) and configure Wi-Fi, VPN, and network settings remotely.

5. Enroll and Monitor Devices

  • For company-owned devices, enroll them via Google Endpoint Manager for centralized oversight

  • Use the device inventory to monitor all registered devices, check compliance, and audit device activity

  • For ChromeOS devices, use the Chrome > Settings > Device section to configure device and user policies, enforce updates, and manage extensions.

6. Automate and Streamline Management

  • Set up automated policy enforcement and alerts using built-in rules or third-party tools like gPanel for advanced automation and reporting

  • Regularly review and update policies to adapt to organizational changes and evolving security needs.

7. Best Practices

  • Segment users and devices into organizational units for tailored policy application

  • Test new policies with pilot groups before organization-wide rollout to avoid disruptions

  • Train users on device enrollment and compliance requirements.

[mai mult...]

How machine learning Works in Google Admin Center

Machine learning (ML) in the context of Google Admin Center (part of Google Workspace/Google Admin Console) operates primarily behind the scenes to enhance productivity, security, and administrative efficiency. While the Admin Center itself is focused on managing users, devices, and policies, many of its intelligent features—such as security alerts, threat detection, and automation—are powered by ML models developed and maintained by Google.

Key Ways Machine Learning Is Used

  • Security and Threat Detection

    • ML models analyze activity patterns across user accounts and devices to detect suspicious behavior, such as phishing attempts, unauthorized access, or malware distribution. These models are trained on vast datasets to recognize anomalies and alert administrators in real time, helping to prevent security breaches.

    • The spam detection system in Gmail, accessible and manageable via Google Admin Center, is a prominent example. Initially rule-based, it now uses ML (including TensorFlow) to dynamically identify and filter spam, adapting quickly to new threats.

  • Automated Policy Recommendations

    • ML can suggest security or compliance policy changes based on observed usage patterns and emerging risks. For example, if a particular group of users is frequently targeted by phishing, the system may recommend stricter authentication policies.

  • Productivity Enhancements

    • Features like “Quick Access” in Google Drive use ML to predict and surface files users are likely to need, based on their activity, time of day, and collaboration patterns. These predictions help users and admins find information faster, reducing overhead.

    • In apps managed through Google Admin Center, ML powers smart features such as Smart Reply in Gmail, Explore in Docs/Sheets/Slides, and automated meeting scheduling, all designed to streamline workflows and reduce repetitive tasks.

  • Generative AI Integration

    • Newer generative AI tools (like Gemini) are being integrated into Google Workspace apps. These tools assist with drafting content, summarizing data, and automating complex workflows, with privacy and data protection controls managed through the Admin Center.

How Machine Learning Is Implemented

  • Model Training and Deployment

    • Google’s ML models are trained on large, anonymized datasets using cloud-based infrastructure. The process involves data preparation, model training, deployment, and ongoing monitoring to ensure accuracy and adapt to new threats or usage patterns.

    • For custom ML workflows (e.g., for organizations building their own models), Google Cloud offers tools like Vertex AI, which supports the full ML lifecycle: data preparation, training, deployment, and monitoring. While this is more relevant for advanced use cases, it is integrated with Google’s broader administrative and security ecosystem.

  • Continuous Learning and Adaptation

    • ML systems in Google Admin Center are continuously updated to learn from new data and improve over time. For example, spam filters and threat detection models are regularly retrained to recognize new attack vectors.

[mai mult...]

How to Administer Spam Filters in Google Admin Center

Google Workspace (formerly G Suite) provides robust spam filtering tools that can be customized and managed through the Google Admin console.

Accessing Spam Filter Settings

  1. Sign in to the Google Admin console using your administrator account.

  2. Navigate to:

    • Menu → Apps → Google Workspace → Gmail → Spam, Phishing, and Malware.

  3. On the left, select the organizational unit (OU) you want to configure. Settings can be applied at the domain or OU level.

Configuring Spam Filtering Options

  • Click Configure or Add another rule in the Spam section.

  • In the Add setting box, enter a unique name for your spam filter rule.

  • Choose from various spam filtering options, such as:

    • Adjusting the aggressiveness of spam detection.

    • Creating content compliance rules.

    • Setting actions for detected spam (quarantine, delete, modify subject, etc.).

Allowlisting (Whitelisting) and Blocklisting

  • Email Allowlist: To ensure emails from specific IPs, domains, or addresses are never marked as spam, use the allowlist option:

    • Click on Email allowlist and enter the IP addresses or domains to always allow.

    • Save your settings.

  • Blocked Addresses: Specify addresses or domains you want to block. You can also configure whether to notify senders when their emails are rejected.

Bypassing Spam Filters for Approved Senders

  • To bypass spam filters for messages from certain senders or domains:

    • In the Spam section, click Configure or Add another rule.

    • Check the boxes for “Bypass spam filters for messages from senders or domains in selected lists” and “Bypass spam filters and hide warnings for messages from senders or domains in selected lists”.

    • Assign an existing list or create a new address list for these senders or domains.

    • Save the rule and allow up to 24 hours for propagation.

Advanced Spam Filtering Options

  • Enhanced Pre-delivery Message Scanning: Enable this to allow Google to perform additional scans on suspicious messages, which may introduce a short delivery delay but improves spam detection.

  • Inbound Gateway: If using an external mail gateway, configure the inbound gateway settings to ensure proper spam evaluation and delivery. Add the gateway IPs and adjust header-based spam detection as needed.

  • SPF, DKIM, DMARC: Implement these DNS records to improve your domain’s email authentication and reduce spam/phishing risks.

Monitoring and Reporting

  • Use the Spam filter report in the Admin console to monitor spam activity, view quarantined messages, and adjust settings as needed.

[mai mult...]

How to integrate DFIR Iris with Wazuh

  1. Locate Customer ID Access the DFIR-IRIS dashboard using an administrator account, then go to Advanced > Customers and choose the customer you wish to integrate. Record the Customer ID.

  2. Retrieve API Key Get the API key for the current DFIR-IRIS user by clicking on the username and choosing My settings. Copy this API key and keep it safe for integrating the Wazuh server.

  3. Create and Configure the Integration Script

    • Create a script file named /var/ossec/integrations/custom-wazuh_iris.py and add the script to forward alerts to DFIR-IRIS.

    • Modify the script by setting the alert_source_link to the Wazuh dashboard IP address and the alert_customer_id to the ID of the customer as it appears on the DFIR-IRIS dashboard.

    • Set the ownership and permissions of the /var/ossec/integrations/custom-wazuh_iris.py file:

      bash
      chmod 750 /var/ossec/integrations/custom-wazuh_iris.py
      chown root:wazuh /var/ossec/integrations/custom-wazuh_iris.py
  4. Configure Wazuh Add the following configuration to the /var/ossec/etc/ossec.conf file to send alerts to DFIR-IRIS:

    xml
    <ossec_config>
    <integration>
    <name>custom-wazuh_iris.py</name>
    <hook_url>https://<IRIS_IP_ADDRESS>/alerts/add</hook_url>
    <level>7</level>
    <api_key><IRIS_API_KEY></api_key>
    <alert_format>json</alert_format>
    </integration>
    </ossec_config>

    Make sure to replace <IRIS_IP_ADDRESS> with the actual IP address of your IRIS instance and <IRIS_API_KEY> with your IRIS API key. You can adjust the <level> to the desired threshold for alerts.

  5. Restart Wazuh Manager Restart the Wazuh manager to apply the changes.

    bash
    service wazuh-manager restart
[mai mult...]

How to start implementing Wazuh

1. Install the Wazuh server The Wazuh server is the central component that collects and analyzes data from Wazuh agents. It consists of the Wazuh manager and Filebeat. The Wazuh manager analyzes data and triggers alerts, while Filebeat forwards alerts and archived events to the Wazuh indexer.

    • You’ll need root user privileges to run the commands.

    • Add the Wazuh repository:

      • For RPM-based systems (CentOS, Red Hat, etc.):

        bash
        rpm --import https://packages.wazuh.com/key/GPG-KEY-WAZUH
        echo -e '[wazuh]\ngpgcheck=1\ngpgkey=https://packages.wazuh.com/key/GPG-KEY-WAZUH\nenabled=1\nname=EL-$releasever - Wazuh\nbaseurl=https://packages.wazuh.com/4.x/yum/\nprotect=1' | tee /etc/yum.repos.d/wazuh.repo
      • For Debian-based systems (Ubuntu, Debian, etc.):

        bash
        apt-get install gnupg apt-transport-https
        curl -s https://packages.wazuh.com/key/GPG-KEY-WAZUH | gpg --no-default-keyring --keyring gnupg-ring:/usr/share/keyrings/wazuh.gpg --import && chmod 644 /usr/share/keyrings/wazuh.gpg
        echo "deb [signed-by=/usr/share/keyrings/wazuh.gpg] https://packages.wazuh.com/4.x/apt/ stable main" | tee -a /etc/apt/sources.list.d/wazuh.list
        apt-get update
    • Install the Wazuh manager package using your system’s package manager.

    • Alternatively, use the Wazuh installation assistant:

      bash
      curl -sO https://packages.wazuh.com/4.11/wazuh-install.sh
      bash wazuh-install.sh --wazuh-server <node_name>

      Replace <node_name> with the name used in config.yml.

    • Disable Wazuh updates to prevent accidental upgrades by executing the following commands:

      • For RPM-based systems:

        bash
        sed -i "s/^enabled=1/enabled=0/" /etc/yum.repos.d/wazuh.repo
      • For Debian-based systems:

        bash
        sed -i "s/^deb /#deb /" /etc/apt/sources.list.d/wazuh.list
        apt update
  1. Install the Wazuh indexer The Wazuh indexer is a scalable full-text search engine that provides security, alerting, and performance analysis.

    • First, generate SSL certificates:

      bash
      curl -sO https://packages.wazuh.com/4.11/wazuh-certs-tool.sh
      curl -sO https://packages.wazuh.com/4.11/config.yml
    • Edit ./config.yml to replace node names and IPs.

    • Run the certificate tool:

      bash
      bash ./wazuh-certs-tool.sh -A
    • Compress the certificate files:

      bash
      tar -cvf ./wazuh-certificates.tar -C ./wazuh-certificates/ .
      rm -rf ./wazuh-certificates
    • Copy the wazuh-certificates.tar file to all nodes.

    • Install any missing package dependencies:

      • For RPM-based systems:

        bash
        yum install coreutils
      • For Debian-based systems:

        bash
        apt-get install debconf adduser procps
    • Add the Wazuh repository (see step 1).

    • Install the Wazuh indexer package.

Install the Wazuh dashboard The Wazuh dashboard provides a web interface for visualizing and managing your security data.

    • Install any missing packages:

      bash
      yum install libcap
    • Install the Wazuh dashboard package:

      bash
      yum -y install wazuh-dashboard
    • Configure the Wazuh dashboard by editing /etc/wazuh-dashboard/opensearch_dashboards.yml5.

    • Deploy the certificates:

      bash
      NODE_NAME=wazuh-demo
      mkdir /etc/wazuh-dashboard/certs
      tar -xf ./wazuh-certificates.tar -C /etc/wazuh-dashboard/certs/ ./$NODE_NAME.pem ./$NODE_NAME-key.pem ./root-ca.pem
      mv -n /etc/wazuh-dashboard/certs/$NODE_NAME.pem /etc/wazuh-dashboard/certs/dashboard.pem
      mv -n /etc/wazuh-dashboard/certs/$NODE_NAME-key.pem /etc/wazuh-dashboard/certs/dashboard-key.pem
      chmod 500 /etc/wazuh-dashboard/certs
      chmod 400 /etc/wazuh-dashboard/certs/*
      chown -R wazuh-dashboard:wazuh-dashboard /etc/wazuh-dashboard/certs
      ll /etc/wazuh-dashboard/certs/
    • Enable and start the Wazuh dashboard service:

      bash
      systemctl daemon-reload
      systemctl enable wazuh-dashboard --now
  1. Install and configure Wazuh agents Deploy Wazuh agents to the endpoints you want to monitor. These agents collect data and send it to the Wazuh server for analysis.

  2. Access the Wazuh web UI Open Kibana in your web browser and navigate to the Wazuh app to view dashboards and alerts.

After installing the Wazuh server and agents, you can monitor and manage your IT environment’s security, customize rules, analyze logs, and configure compliance policies.

[mai mult...]

PowerShell script to retrieve security-related events

PowerShell script to retrieve security-related events from the Windows Event Log, specifically from the Security log.

# Define the log name and security-related event IDs (adjust as needed)
$logName = “Security”
$securityEventIDs = @(4624, 4625, 4672, 4688, 4634, 4648, 4768, 4776) # Common security event IDs

# Get security events from the Windows Event Log
$securityEvents = Get-WinEvent -LogName $logName -MaxEvents 50 | Where-Object { $_.Id -in $securityEventIDs }

# Display the results
if ($securityEvents) {
foreach ($event in $securityEvents) {
Write-Output “———————————-”
Write-Output “Time: $($event.TimeCreated)”
Write-Output “Event ID: $($event.Id)”
Write-Output “Message: $($event.Message)”
}
} else {
Write-Output “No security events found.”
}

Event ID Description
4624 Successful login
4625 Failed login
4672 Special privileges assigned (admin logins)
4688 A new process was created
4634 Logoff event
4648 Explicit credential logon (RunAs)
4768 Kerberos authentication (TGT request)
4776 NTLM authentication attempt
[mai mult...]

PowerShell script to retrieve VPN events

PowerShell script to retrieve VPN events from the Windows Event Log. It focuses on events related to VPN connections (RAS and IKEv2).

# Define the log name and event IDs for VPN connections
$logName = “Application”
$vpnEventIDs = @(20225, 20226, 20227, 20255) # Example VPN event IDs

# Retrieve VPN connection events from the Event Log
$vpnEvents = Get-WinEvent -LogName $logName | Where-Object { $_.Id -in $vpnEventIDs }

# Display the results
if ($vpnEvents) {
foreach ($event in $vpnEvents) {
Write-Output “———————————-”
Write-Output “Time: $($event.TimeCreated)”
Write-Output “ID: $($event.Id)”
Write-Output “Message: $($event.Message)”
}
} else {
Write-Output “No VPN events found.”
}

  • Queries the Windows Event Log for VPN-related events
  • Filters based on event IDs typically associated with VPN connections
  • Displays relevant event details.
[mai mult...]