Altanova SIEM Dashboard
Microsoft Sentinel · Defender · Entra ID
Refreshing your Dashboard
Restoring your session
Status:
Processing…
Please wait
0 / 0 0%
✓ Done
0 selected

🗄 Archive as Group

Enter a description for this group of resolved alerts. All selected alerts will be archived together under this name.

📦 Add to existing group (optional)
🗂 Archive Folder (optional)

Mark as Resolved

What would you like to do with this alert?

🗂 Archive Folder (optional)
Archived Alerts
 
0
Total
0
Critical
0
High
0
Medium
0
Low
0
Info
🗄
No archived alerts yet. Resolved alerts you choose to archive will appear here.
0 selected

Create Archive Group

Manage Groups

Existing Groups

Add to Group

Select a group to merge the selected alerts into:

Rename Group

🗑

Delete Permanently

This action cannot be undone

Are you sure you want to permanently delete the selected items?

Security Health
Microsoft 365 security posture overview · Live data when connected to Azure  
Company Security Score
/ 100
Posture
Computed from active alerts
0
Critical
0
High
0
Medium
0
Low
0
Info
Based on active alert severity — connect Azure for live Microsoft Secure Score
Microsoft Secure Score Sample
/ —
—% of max achieved
Identity
Data
Apps
Benchmark vs Other Companies ● Your score
All tenants
global Microsoft avg
Similar size
same seat count
Your industry
same sector avg
Sample data — connect Azure for live score
Device Compliance Sample
%
✓ Compliant
✗ Non-compliant
Connect to Azure for live data
Metrics & Analytics
Alert volume, severity distribution, and source breakdown  
Total Alerts
0
Resolved Today
0
False Positives
0
Open Critical
0
Alert Volume by Severity
Alerts by Source
User & Entity Risk Scores
Ranked by composite risk score · includes active & archived alerts  
🔗
Microsoft Security Portals
Quick access to all Microsoft security & administration portals · click any card to open  ACTIF — Quick Access
Microsoft Sentinel
Cloud-native SIEM — investigate incidents, hunt threats, manage analytics rules
portal.azure.com
Microsoft Defender XDR
Unified security portal — alerts, incidents, hunting, secure score
security.microsoft.com
Microsoft 365 Admin
Manage Microsoft 365 subscriptions, users, licenses and service health
admin.microsoft.com
SharePoint Admin
Manage SharePoint sites, permissions, storage, and sharing policies
SharePoint Admin Center
Azure Portal
Full Azure resource management — subscriptions, policies, infrastructure
portal.azure.com
Microsoft Entra ID
Manage identities, MFA, Conditional Access, and privileged roles
entra.microsoft.com
Microsoft Purview
Data governance, DLP, information protection, compliance and audit management
purview.microsoft.com
Microsoft Intune
Endpoint management, device compliance, and mobile app policies
intune.microsoft.com
Exchange Admin
Manage mailboxes, mail flow rules, transport rules, and spam filters
Exchange Admin Center
Defender for Cloud Apps
Monitor cloud app usage, shadow IT, and apply CASB policies
security.microsoft.com
Microsoft Secure Score
Track and improve your organisation's security posture with action items
security.microsoft.com
Defender for Cloud
Cloud security posture management (CSPM) and workload protection across Azure
portal.azure.com
Security Exposure Mgmt
Attack surface management, exposure insights and critical asset protection
security.microsoft.com
Service Health
Live Microsoft 365 and Azure service health, incidents and advisories
M365 Admin Center
📋
Incident Remediation Playbooks
10 incident playbooks · select a scenario to see step-by-step response · click Launch Runbook for the full interactive checklist  ACTIF — Playbooks
Incident Types · 10 Playbooks
🔒
Ransomware Attack
CRITICAL
🎣
Phishing / Email Attack
HIGH
🦠
Virus / Malware Infection
HIGH
🔓
Account Compromise
HIGH
📤
Data Exfiltration
CRITICAL
🔨
Brute Force / Password Spray
MEDIUM
👑
Privileged Account Compromise
CRITICAL
🕵
Insider Threat
HIGH
🌊
DDoS / Network Attack
HIGH
📱
Lost / Stolen Device
HIGH
🔒
Ransomware Attack
Mass file encryption · shadow copy deletion · lateral spread via SMB
CRITICAL
    1
    Immediate Isolation
    Disconnect the affected device from the network — remove Ethernet cable or disable the NIC. Do NOT power off — preserve forensic memory for analysis.
    2
    Scope Assessment
    Identify all devices on the same network segment, shared drives, and mapped drives. Check for encrypted file extensions across the environment.
    3
    Account Lockdown
    Reset passwords for all accounts that logged into the affected device in the past 24h. Revoke all Azure AD sessions via Entra ID → Users → Revoke Sessions.
    4
    Identify the Strain
    Collect the ransomware note, encrypted file extensions, and samples. Check nomoreransom.org for known decryptors before paying any ransom.
    5
    Cloud Audit
    Check SharePoint, OneDrive, and Teams for encrypted files uploaded from the infected device during the attack window.
    6
    Backup Validation
    Verify offline backup integrity before considering restoration. Never restore from a backup that was mounted on an infected system.
    7
    Recovery
    Restore from a clean verified backup or reimage from a known-good baseline. Reconnect only after full Defender AV clearance.
    8
    Post-Incident Hardening
    Review patch levels, disable SMBv1, deploy EDR on all endpoints, enable Controlled Folder Access, and run user phishing awareness training.
🏅
SOC 2 Compliance Guide
Complete reference — explained, environment check, audit process & Type 1 / Type 2 roadmap  ACTIF — Reference Guide
📖 SOC 2 Explained
⚖ SOC 2 Type 1 vs Type 2
🔍 Environment Check
📋 Audit Process Information
✅ Audit Process
🏛
What is SOC 2?
SOC 2 (System and Organization Controls 2) is an auditing standard developed by the AICPA. It evaluates how a service organization manages customer data to protect its security, availability, and confidentiality.

Unlike ISO 27001 (a certification), SOC 2 produces an attestation report issued by a licensed CPA firm — the de-facto trust standard for cloud and SaaS companies in North America, increasingly required by enterprise customers worldwide.

Who needs it? Any company that stores, processes, or transmits customer data — SaaS vendors, cloud providers, MSPs, data processors, and B2B technology companies.
🔐
Trust Services Criteria (TSC)
SOC 2 is built on five Trust Services Criteria defined by the AICPA. Only Security is mandatory:
🔒 Security (CC) — Required ⏱ Availability (A) ⚙ Processing Integrity (PI) 🔐 Confidentiality (C) 🛡 Privacy (P)

Security (CC) — Logical/physical access, change management, risk assessment, monitoring & incident response (CC1–CC9, COSO framework).
Availability (A) — System is available as committed.
Processing Integrity (PI) — Processing is complete, valid, accurate & timely.
Confidentiality (C) — Confidential information is protected.
Privacy (P) — Personal data handled as committed (GDPR/PIPEDA aligned).
📐
Common Criteria (CC1–CC9) Breakdown
All SOC 2 reports must address these 9 CC groups:
  • CC1 Control environment — governance, ethics, accountability
  • CC2 Communication & information
  • CC3 Risk assessment — identify & analyze risks
  • CC4 Monitoring activities — detect deficiencies
  • CC5 Control activities — policies & procedures
  • CC6 Logical & physical access controls (largest section)
  • CC7 System operations — anomaly detection, incident management
  • CC8 Change management — SDLC, vulnerability management
  • CC9 Risk mitigation — vendor management, insurance
🎯
Defining Your Scope
The in-scope system is the product or service your customers rely on. It includes the people, processes, and technology supporting it:

Infrastructure — Cloud hosting (Azure), networks, databases, endpoints
Software — Application code, SaaS tools, third-party services
People — Employees and contractors who access in-scope data
Procedures — Policies, runbooks, change management processes

💡 Narrow scope = lower cost. Excluding systems that don't touch customer data can reduce audit effort by 30–50%.
📄
What's Inside a SOC 2 Report?
A SOC 2 report contains 5 sections:

Section I — Independent auditor's report & opinion
Section II — Management's assertion
Section III — System description (infrastructure, software, people, processes)
Section IV — Trust Services Criteria with listed controls
Section V — Other information (management responses to exceptions)

Opinion types:
Unqualified — Clean report, no material issues
Qualified — Exceptions noted, controls partially effective
Adverse — Controls not effective (rare, very serious)
How to read this check: This assessment maps your Microsoft / Azure environment to SOC 2 Common Criteria controls. Green items are capabilities your stack already provides. Amber items require configuration or activation. Red items require processes, documentation, or tools outside the Microsoft stack.
✅ Already Covered by Your Microsoft Environment
Multi-Factor Authentication (CC6.1)
Entra ID provides MFA with FIDO2, Microsoft Authenticator, SMS, and phishing-resistant authentication. Entra ID Conditional Access
Role-Based Access Control (CC6.1, CC6.3)
Azure RBAC and Entra ID groups enforce least-privilege access. PIM provides just-in-time privileged access. Entra PIM Azure RBAC
Audit Logging & SIEM (CC7.2, CC7.3)
Microsoft Sentinel ingests logs from Entra ID, M365, Azure, and endpoints. Retention configurable to 90+ days. Sentinel Log Analytics
Intrusion Detection & Alerting (CC7.1)
Defender XDR and Sentinel provide real-time threat detection, analytics rules, and incident correlation. Defender XDR Sentinel Analytics
Encryption at Rest & in Transit (CC6.7)
Azure encrypts all data at rest (AES-256) and in transit (TLS 1.2+) by default. Customer-managed keys available via Key Vault. Azure Storage Key Vault
Data Loss Prevention (CC6.7, Confidentiality)
Purview DLP policies prevent sensitive data exfiltration via email, SharePoint, endpoints. Sensitivity labels classify data. Purview DLP Sensitivity Labels
Endpoint Protection (CC6.8, CC7.1)
Defender for Endpoint provides EDR, AV, attack surface reduction, and device compliance enforcement. Defender for Endpoint Intune
Vulnerability Management (CC8.1)
Defender for Cloud and Defender for Endpoint provide vulnerability scanning, CVE tracking and prioritised remediation. Defender for Cloud Secure Score
Conditional Access Policies (CC6.1, CC6.6)
Block untrusted locations, require compliant devices, enforce MFA for high-risk logins. Covers all Microsoft 365 and Azure resources. Conditional Access
Identity Protection & Risk Scoring (CC6.1)
Entra ID Protection detects risky sign-ins, impossible travel, and leaked credentials. Risk-based Conditional Access policies auto-respond. Entra ID Protection
Security Posture Score (CC4.1)
Microsoft Secure Score and Defender for Cloud provide a continuous, quantified measure of posture with improvement recommendations. Secure Score
Change Management Logging (CC8.1)
Azure Activity Log, Entra Audit Log, and M365 Unified Audit Log capture all configuration and administrative changes. Activity Log Audit Log
⚠ Available But Needs Configuration / Activation
Log Retention ≥ 90 Days (CC7.2)
Default Entra/M365 audit log retention is 90 days (E3) or 180 days (E5). SOC 2 Type 2 requires logs for the full audit period. Configure Log Analytics workspace with 1-year retention. Log Analytics
Privileged Access Workstations (CC6.1)
PIM is available but may not be fully configured. Ensure all Global Admin and privileged roles require PIM activation with justification and approval workflows. Entra PIM
Backup & Recovery Testing (A1.2, A1.3)
Azure Backup is available but recovery testing must be documented and scheduled. SOC 2 requires evidence of periodic restore tests with recovery time objectives (RTO/RPO). Azure Backup Site Recovery
User Access Reviews (CC6.2, CC6.3)
Entra ID Access Reviews exist but must be configured with periodic (quarterly) reviews of all privileged roles and application assignments. Reviews must produce evidence. Entra Access Reviews
Network Segmentation & Firewalls (CC6.6)
Azure VNets and NSGs can enforce segmentation but must be explicitly configured. Document your network topology, perimeter controls, and NSG rule justifications. Azure Firewall NSG
Insider Risk Management (CC9.2)
Purview Insider Risk Management is available in E5 or as an add-on. Configure policies to detect data theft, leakage by departing employees. Purview IRM
❌ Not in Microsoft's Stack — Requires Process / Documentation
Important: These gaps are common to almost all organisations regardless of their cloud platform. They require written policies, documented procedures, and operational evidence — not just technology.
Written Information Security Policy (CC1.1, CC2.2)
A documented IS policy signed off by leadership, covering acceptable use, data classification, incident response, and access control — reviewed annually.
Formal Risk Assessment (CC3.1, CC3.2)
Annual risk register with identified threats, likelihood/impact scoring, and treatment decisions. Must be reviewed by management and updated regularly.
Security Awareness Training (CC1.4, CC2.2)
All employees must complete documented security training at hire and annually. Evidence: training completion records, phishing simulation results. Microsoft Viva Learning or KnowBe4.
Vendor / Third-Party Risk Management (CC9.2)
Formal vendor inventory with risk classification, security questionnaires (SIG/CAIQ), and evidence of periodic vendor reviews. Especially for sub-processors handling customer data.
Incident Response Plan & Evidence (CC7.3, CC7.4, CC7.5)
A documented IR plan with defined roles, escalation paths, communication templates, and post-incident review process. Type 2 requires evidence of actual incidents being handled per the plan.
Change Management Procedure (CC8.1)
Documented SDLC / change control process: code review requirements, testing gates, approval workflows, rollback procedures. Tickets and PR history serve as evidence for Type 2.
Business Continuity / Disaster Recovery Plan (A1.2)
Documented BCP/DRP with defined RTO/RPO, recovery steps, communication tree, and tested recovery procedures. Annual tabletop exercises with documented outcomes.
Background Check Process (CC1.1)
Pre-employment background screening policy for employees and contractors with access to in-scope systems. Document the process and retain completion records.
Penetration Testing (CC4.1, CC7.1)
Annual third-party pen test scoped to in-scope systems. Report with findings, CVSS scoring, and documented remediation. Required for most enterprise SOC 2 customers.
Offboarding Procedure (CC6.2)
Formal documented checklist for revoking all access within 24h of termination: Entra ID accounts, VPN, third-party apps, physical access. Evidence for each offboarding event.
Two parallel tracks are shown below. Steps marked 🔵 apply to both Type 1 and Type 2. Steps marked 🟣 are additional requirements for Type 2 only. Estimated timelines are for a mid-size organisation completing their first SOC 2 audit.
1
Scope Definition & Readiness
🔵 Both Types · 3–5 weeks
  • Define the system boundary: Document every service, application, infrastructure component, and data store that processes customer data. Create a system description document.
  • Select Trust Services Criteria: At minimum Security (CC). Add Availability if you have uptime SLAs, Confidentiality for data protection obligations, Privacy if you handle PII under GDPR/CCPA.
  • Assign internal ownership: Designate a SOC 2 project lead (typically CISO or CTO), executive sponsor, and a control owner for each CC group. Map CC1–CC9 to responsible teams.
  • Microsoft-specific actions: Export your Entra ID tenant settings, Conditional Access policies, Defender configuration, and Sentinel workspace structure as baseline documentation. Entra ID Defender Sentinel
  • Select your auditor early: Issue RFPs to 3–5 AICPA-licensed CPA firms with SOC 2 experience. Shortlist based on industry experience, timeline, and price. Sign the engagement letter before starting remediation.
2
Gap Assessment & Remediation Planning
🔵 Both Types · 4–6 weeks
  • Map controls to TSC: For each CC sub-criterion, identify your existing controls. Use the AICPA's SOC 2 criteria matrix or a GRC tool (Drata, Vanta, Secureframe, Tugboat Logic) to track mappings.
  • Conduct internal gap analysis: Walk through every CC point: "Do we have a control? Is it documented? Is there evidence?" Document gaps in a remediation tracker with priority, owner, and target date.
  • Prioritise critical gaps: Focus first on CC6 (access controls), CC7 (monitoring), and CC8 (change management) — these have the most sub-criteria and the highest auditor scrutiny.
  • Microsoft Secure Score review: Run your Secure Score improvement actions and address critical recommendations. Export the Secure Score report as evidence of your security posture baseline. Secure Score
  • Review vendor list: Inventory all third-party services (CRMs, CDNs, payment processors) that access customer data. Collect their SOC 2 or ISO 27001 reports. Begin a formal vendor risk register.
3
Policy Writing & Control Implementation
🔵 Both Types · 5–8 weeks
  • Write or update core policies: Information Security Policy, Acceptable Use Policy, Access Control Policy, Incident Response Policy, Change Management Policy, Vendor Management Policy, Business Continuity Plan, Data Retention & Disposal Policy.
  • Implement technical controls: Enable Entra PIM for all privileged roles, configure Access Reviews (quarterly), enforce MFA via Conditional Access, set log retention ≥ 1 year in Log Analytics workspace. Entra PIM Conditional Access
  • Configure Sentinel detection rules: Enable scheduled analytics rules for failed logins, privilege escalation, impossible travel, data exfiltration, and log deletion. These alerts are key evidence for CC7. Sentinel Analytics
  • Deploy security awareness training: Enrol all employees in a training platform. Run a baseline phishing simulation. Record completion rates. Set a quarterly cadence for reminders.
  • Perform penetration test: Commission a third-party pen test scoped to in-scope systems. Remediate all Critical/High findings before the audit. Retain the final report and remediation evidence.
  • Get board/executive sign-off: All policies must be formally approved by leadership. Use DocuSign or similar — retain signed copies as evidence for CC1.1 (tone at the top).
🔵 Type 1 Path — Evidence Submission
4
Auditor Evidence Submission
4–6 weeks
  • Set the as-of date: A Type 1 report is valid for one specific date (e.g., "as of March 31, 2026"). All evidence — screenshots, configurations, policy versions — must reflect that date.
  • Prepare the evidence package: For each control, collect: (1) the relevant policy, (2) a configuration screenshot or export, (3) a logical access list (who has what access), (4) a description of how the control works.
  • Key Microsoft evidence to export: Entra ID users list, role assignments, MFA report, Conditional Access policies · Sentinel analytics rules · Defender enrolled devices · Azure RBAC assignments. Entra ID Sentinel Defender
  • Auditor walkthrough sessions: Schedule 1–3 hour sessions for each CC group. Walk the auditor through your controls with a screen share — "inquiry" is a primary evidence type for Type 1.
  • Management assertion letter: Sign and submit the management assertion confirming the system description is accurate and controls are in place. Have legal review it.
  • Address deficiencies: Work with auditors on management responses — remediate or explain a compensating control. A few minor exceptions are normal.
Month 1–2: Scope, gap assessment, auditor selection
Month 2–4: Policy writing, control implementation, pen test
Month 4–5: Evidence collection, auditor walkthroughs
Month 5–6: Draft review, management assertion, final report
⏱ Total: 4–6 months  ·  💰 $15K–$35K
🟣 Type 2 Path — Observation + Testing
4b
Observation Period (Operating Effectiveness)
6–12 months
  • Start the observation period: Agree on start and end dates with your auditor (min 6 months; 12 months for a full annual report). Every control must operate consistently throughout this period.
  • Automate evidence collection: Integrate your Microsoft stack with a GRC tool (Drata, Vanta) to auto-collect screenshots and reports daily. Drata Vanta
  • Run quarterly access reviews: Use Entra ID Access Reviews to generate quarterly reports. Export the review results as evidence. Entra Access Reviews
  • Document every incident: All security incidents must be logged, investigated, and closed per your IR plan. Auditors request a complete incident register. Sentinel Incidents
  • Maintain change log evidence: Every production change must go through your change management process. Auditors will sample PRs, tickets, and approval records. Azure Activity Log
  • Track training completion: Ensure 100% of employees complete annual security training. Run at least one phishing simulation and document results.
  • Annual pen test: At least one pen test must fall within or shortly before the audit period. Retain the report, findings, and remediation evidence.
5
Auditor Testing & Sampling
6–10 weeks
  • Population testing: Auditors select a statistical sample — e.g., 25 access provisioning tickets, 10 change approvals, 15 offboarding events. Provide evidence for every sample requested.
  • Log analysis: Auditors review Sentinel logs, Entra sign-in logs, and Azure Activity Logs to verify controls operated during the period. Sentinel Log Analytics
  • Re-performance testing: For key controls, auditors may re-run tests themselves — e.g., attempt a login from an untrusted network to verify Conditional Access blocks it. Conditional Access
  • Exceptions management: Document root cause, impact, and remediation for any exceptions. A small number with strong management responses rarely prevent a clean opinion.
  • Draft report review: Review carefully — this is your last opportunity to correct factual errors or add management responses before issuance.
Month 1–3: Scope, gap, remediation (parallel to Type 1 or standalone)
Month 3–15: 12-month observation period, continuous evidence collection
Month 13–17: Auditor fieldwork, sampling, log review
Month 17–18: Draft review, management assertions, final report
⏱ Total: 15–18 months  ·  💰 $30K–$100K+
6
Report Issuance & Continuous Compliance
🔵 Both Types · Ongoing
  • Receive the final report: The auditor issues the signed SOC 2 report (Type 1 or Type 2) with their opinion letter. The report is typically 50–150 pages including system description, controls, and testing results.
  • Distribute under NDA: SOC 2 reports are confidential. Share only with customers and prospects who sign an NDA or a specific "report recipient" letter. Never post publicly — only a SOC 2 summary letter or badge goes on your website.
  • Begin next audit cycle: For Type 2, the next observation period begins the day after the previous one ends. There should be no gap. Update your engagement letter with your auditor before the end of each period.
  • Remediate report findings: Create a remediation plan for every exception noted. Track completion in your GRC tool. Demonstrate improvement in the next report cycle.
  • Maintain continuous monitoring: SOC 2 is not a point-in-time exercise anymore. Use this dashboard with Sentinel alerts, Defender Secure Score, and Entra Access Reviews to maintain posture year-round. This Dashboard Sentinel Secure Score
💡 Recommended tooling for Microsoft environments: Consider integrating Drata or Vanta with your Microsoft 365 tenant. These GRC platforms natively connect to Entra ID, Defender, Azure, and Intune to automatically collect evidence, alert on control failures, and generate audit-ready reports — reducing audit prep time by 60–80%.
SOC 2 Type 1 vs Type 2 — Key Differences
Type 1 asks "Are the controls designed correctly?"  ·  Type 2 asks "Are they actually working, consistently, over time?"
Criteria▸ Type 1▸ Type 2
ScopeSingle snapshot dateObservation period — min 6 months, typically 12
What is testedDesign & implementation of controlsDesign + operating effectiveness over time
EvidencePolicies, procedures, configuration screenshotsLogs, tickets, reviews, exceptions — all dated during the period
Auditor testingInquiry & inspection onlyInquiry, inspection, observation, re-performance
Timeline2–4 months total9–18 months total (inc. observation period)
Cost$15,000 – $35,000 USD$30,000 – $100,000+ USD
Market valueGood starting pointGold standard — required by most enterprise customers
Best forNew companies, quick compliance, pre-salesOngoing compliance, mature programs, enterprise deals
RenewalOne-time or annual snapshotAnnual — covers the trailing 12 months
💡 Best practice: Start with Type 1 to establish a baseline, then immediately begin the Type 2 observation period. Most companies achieve their first Type 2 report 12–18 months after starting.
SOC 2 Audit Progress
0%
0 of 49 tasks completed across 9 phases
Completed0
In Progress0
Blocked0
Not Started0
🛡
Security Incident Log
Altanova · Version 1.0 · March 2026 · Owner: Altanova  
By Severity
By Type
ID Date Reported Incident Title Type Severity Priority Status Assigned To
Reference Guide — Types, Severities, Statuses & Priorities
Incident Types
🦠 Malware / Ransomware🎣 Phishing / Social Engineering🔓 Unauthorized Access📤 Data Breach / Exfiltration💥 Denial of Service (DoS/DDoS)🕵 Insider Threat🏢 Physical Security⚙ System Misconfiguration💻 Lost / Stolen Device📌 Other
Severity Levels
Critical — Immediate threat, major impact High — Significant risk, fast action needed Medium — Moderate impact, planned response Low — Minor, informational or awareness
Statuses & Priorities
Open In Progress Contained Resolved Closed
P1 – Immediate P2 – Urgent P3 – Normal P4 – Low
✏ Edit mode — modify any field below, then click Save Changes
📊
SharePoint Usage
Site storage, user activity & file operations — pulled from Microsoft Graph Reports API  
Connect to Microsoft to load SharePoint data.
🌐
Total Sites
All SharePoint sites
Active Sites
With file activity
👤
Active Users
In selected period
📁
Total Files
Across all sites
📂
Active Files
Viewed or edited
🔗
Page Visits
In selected period
used
💾 Tenant Storage Usage
📤 Storage Used
📊 Utilization
📅 As of Date
📈 File Activity Breakdown
👁️
Viewed / Edited
Files opened or modified
🔄
Synced
Via OneDrive sync client
🏢
Shared Internally
↗ Click to explore files
🌍
Shared Externally
↗ Click to explore files
Top Sites by Storage
Relative storage share across all sites
#
Site
Storage
Active Files ↕ period
Connect to Microsoft to load site data.
Storage Trend
Tenant total storage usage over time (GB)
No trend data available
ℹ️ Requires Sites.Read.All permission in Azure AD. Search for any site to view its permission entries and navigate to it directly.
🏆 Top Sites by Activity — hover to act
Load SharePoint Usage first to see top sites here.
or search by name
🔍
Search for a site above to view its permissions.
Orange border = item has explicit sharing (link, external user, or specific people)
🔐Click a folder (Col 2) or a file (Col 3) to view its permissions in Col 4
🌐 Sites
0
Connect to Microsoft and load SharePoint data first,
or click next to Sites to load sites directly.
📁 Folders
Select a site
to browse folders
📄 Files
Select a folder
to view its files
🔐 Permissions
Select a file or folder
to view its permissions
Policy Name
📋 Description
Policy ID
Alerts Triggered
Created
Last Modified
Risk Score Threshold
Assigned To
🔎 Filters & Conditions
⚡ Governance Actions
↗ Open policy in Microsoft Defender for Cloud Apps
Alerts (0)
Alert Severity Status Source Created
🎓
Cybersecurity Training Log
Altanova · Track training sessions, completion status & scores per user  ACTIF — Local Records
By Training Type
By Status
ID Date User Training Type Delivery Status Score Duration
✏ Edit mode — modify any field below, then click Save Changes

⚙ Azure Connection Settings

🔒 Settings Password

Not connected — enter your Azure credentials below.

Azure AD App Credentials

Paste the Tenant ID and Client ID from your Azure App Registration. No client secret is stored — you'll sign in with your Microsoft account.

🔗 Connect Defender for Cloud Apps Policies

Auto-Refresh

ESET PROTECT Cloud Credentials

📁 Proxy Folder

📋 One-Time Azure Setup (5 min)

👥 Team Members

🔔 Notifications

👁 Watchlist

IN PROGRESS
Analyst Security Team
Opened
Elapsed 00:00:00
Steps Done 0 / 0
Completion
0%
✅ Incident Resolved — All steps completed. Document this incident in your incident log.
Hardware Asset Detail
CPU
RAM
Storage
GPU
🔧 Hardware Specifications
💻 Software & OS
Software License Detail
Vendor
License
Seats
Renewal