search authority

How to Use 360 Security Cloud: A Step‑by‑Step Evergreen Guide

By Elena Carter4 min read 670 views
Featured image for How to Use 360 Security Cloud: A Step‑by‑Step Evergreen Guide
How to Use 360 Security Cloud: A Step‑by‑Step Evergreen Guide

What Is 360 Security Cloud?

360 Security Cloud is a unified, cloud‑native security platform that combines endpoint protection, web filtering, vulnerability management, and security information and event management (SIEM) into a single SaaS offering. Built by Qihoo 360, the service is designed for enterprises and SMBs that want centralized visibility and automated response without managing on‑prem hardware.

More from this site

Keep reading the latest coverage

Browse latest →

Why Choose a Cloud‑Based Security Solution?

Cloud security platforms deliver three core benefits: (1) Scalability – resources grow with your user base; (2) Continuous updates – threat intel is refreshed in real time; and (3) Lower total cost of ownership – no CAPEX for appliances or dedicated staff for patching.

Getting Started: Account Creation and Initial Setup

1. Sign Up for a 360 Security Cloud Account

Visit the official 360 Security Cloud portal, choose a subscription tier (Enterprise, Business, or Starter), and complete the registration form. You will receive a verification email and an initial admin login link.

2. Verify Domain Ownership

To enable web filtering and SIEM integration, you must verify ownership of your corporate domain. Follow the DNS TXT‑record method provided in the admin console, then click "Verify".

3. Add Users and Devices

Navigate to **Identity & Access Management** → **Users**. You can import users via CSV, sync with Azure AD, or use SSO (SAML) for automatic provisioning. For devices, download the lightweight 360 Agent for Windows, macOS, Linux, iOS, and Android, then push it through your existing endpoint management tool.

Core Configuration Areas

Endpoint Protection

Once agents are installed, enable the following modules:

  • Real‑time malware scanning
  • Behavior‑based ransomware detection
  • Application control (whitelisting/blacklisting)

Set the default policy to "Block high‑risk detections" and schedule a weekly full system scan.

Web Filtering

Under **Policy > Web Filtering**, create categories (e.g., Social Media, Streaming, Gambling) and assign risk levels. Use the pre‑built "Global Threat Intelligence" list to block known malicious URLs automatically.

Vulnerability Management

Enable the built‑in vulnerability scanner to run nightly across all registered assets. Prioritize patches using the CVSS score column and integrate with your ticketing system (Jira, ServiceNow) via the provided API webhook.

SIEM & Incident Response

Activate the SIEM module to collect logs from firewalls, cloud services, and the 360 agents. Create correlation rules such as "Multiple failed logins + new process creation". When a rule triggers, the platform can automatically isolate the affected endpoint.

Integrations and Automation

360 Security Cloud supports native integrations with major SaaS tools. The table below summarizes the most common connections.

IntegrationPrimary UseSource Type
Azure AD / Okta (SSO)User provisioning & MFAOfficial connector
ServiceNowTicket auto‑creationAPI webhook
SplunkLog forwardingSyslog output
SlackAlert notificationsWebhook

Best Practices for Ongoing Management

  • Regular policy review – quarterly audit of web‑filter categories and endpoint rules.
  • Threat intel updates – ensure the "Global Threat Intelligence" feed is set to auto‑update daily.
  • Backup configurations – export policy JSON files before major changes.
  • User education – run quarterly phishing simulations using the platform's built‑in campaign tool.

Common Issues and Troubleshooting

Agent fails to communicate

Check outbound TCP ports 443 and 8443 are open. Verify the device's time sync; mismatched certificates often cause handshake failures.

False positives in web filtering

Use the "Allow" list to whitelist business‑critical URLs. Review the "Detection Log" to adjust risk thresholds.

SIEM data overload

Apply log retention policies: keep high‑severity events for 90 days, lower‑severity for 30 days. Use the built‑in "Log Sampling" feature to reduce volume.

FAQ – Quick Answers

  • Is there a free tier? A 30‑day trial is available; after that, the smallest paid tier starts at $4 per endpoint per month.
  • Can I use 360 Security Cloud with existing firewalls? Yes, it integrates via API or syslog; you do not need to replace hardware.
  • Does it meet GDPR/CCPA requirements? The platform offers data‑residency options in EU and US regions and includes built‑in data‑subject request tooling.

Editor's pick

Keep exploring our latest stories

Fresh reads, picked daily.

Browse latest
Share: