Initial commit - 611 cybersecurity skills across all subdomains

This commit is contained in:
mukul975
2026-02-25 10:47:44 +01:00
commit 22a7ab1462
1765 changed files with 280648 additions and 0 deletions
@@ -0,0 +1,164 @@
---
name: implementing-mobile-application-management
description: >
Implements Mobile Application Management (MAM) policies to protect enterprise data on managed
and unmanaged mobile devices through app-level controls including data loss prevention, selective
wipe, app configuration, and containerization. Use when securing corporate apps on BYOD devices,
implementing Intune App Protection Policies, or enforcing data separation between personal and
work apps. Activates for requests involving MAM deployment, app protection policies, mobile
containerization, or BYOD security.
domain: cybersecurity
subdomain: mobile-security
author: mahipal
tags: [mobile-security, android, ios, mam, enterprise-security, owasp-mobile]
version: 1.0.0
license: MIT
---
# Implementing Mobile Application Management
## When to Use
Use this skill when:
- Deploying enterprise mobile app protection without full device management (MDM)
- Implementing BYOD policies that protect corporate data while respecting personal privacy
- Configuring Microsoft Intune App Protection Policies for iOS and Android
- Enforcing data loss prevention controls on managed mobile applications
**Do not use** when full device management (MDM) is already deployed and sufficient -- MAM adds complexity when MDM already provides the needed controls.
## Prerequisites
- Microsoft Intune or equivalent MAM platform (VMware Workspace ONE, MobileIron)
- Azure AD for identity and conditional access policies
- Intune App SDK integrated into target applications (or Intune App Wrapping Tool)
- Test devices (Android 10+ and iOS 15+)
- Azure AD Premium P1 or P2 licenses for conditional access
## Workflow
### Step 1: Define App Protection Policy Requirements
Classify data sensitivity and define protection tiers:
| Tier | Data Type | Controls |
|------|-----------|----------|
| Tier 1 - Basic | General corporate email | Require PIN, block screenshots |
| Tier 2 - Enhanced | Financial data, HR records | Encrypt app data, restrict cut/copy/paste |
| Tier 3 - High | PII, healthcare, legal | Selective wipe, offline access limits, DLP |
### Step 2: Configure Intune App Protection Policies
**Android App Protection Policy:**
```json
{
"displayName": "Corporate App Protection - Tier 2",
"platform": "android",
"dataProtectionSettings": {
"allowedDataStorageLocations": ["oneDriveForBusiness", "sharePoint"],
"blockDataTransferToOtherApps": "managedApps",
"blockDataTransferFromOtherApps": "managedApps",
"saveAsBlocked": true,
"clipboardSharingLevel": "managedAppsWithPasteIn",
"screenCaptureBlocked": true,
"encryptAppData": true,
"backupBlocked": true
},
"accessSettings": {
"pinRequired": true,
"minimumPinLength": 6,
"biometricEnabled": true,
"offlineGracePeriod": 720,
"offlineWipeInterval": 90
},
"conditionalLaunchSettings": {
"maxOsVersion": "15.0",
"minOsVersion": "12.0",
"jailbreakBlocked": true,
"maxPinRetries": 5
}
}
```
### Step 3: Implement App Configuration Policies
Deploy managed app configuration for automatic endpoint setup:
```json
{
"displayName": "Email App Configuration",
"targetedManagedApps": ["com.microsoft.outlooklite"],
"settings": [
{"key": "com.microsoft.outlook.EmailProfile.AccountType", "value": "ModernAuth"},
{"key": "com.microsoft.outlook.EmailProfile.ServerName", "value": "outlook.office365.com"},
{"key": "com.microsoft.outlook.EmailProfile.AllowedDomains", "value": "corporate.com"}
]
}
```
### Step 4: Deploy Conditional Access Integration
```
Azure AD > Conditional Access > New Policy:
- Users: All users with corporate apps
- Cloud apps: Office 365, custom LOB apps
- Conditions: All platforms
- Grant: Require app protection policy
- Session: App enforced restrictions
```
### Step 5: Test and Validate MAM Controls
Test each policy control on both platforms:
```bash
# Verify data transfer restrictions
1. Open managed app (Outlook)
2. Copy text from email body
3. Attempt paste in unmanaged app (Notes) -- should be blocked
4. Attempt paste in managed app (Teams) -- should work
# Verify selective wipe
1. Enroll test device with MAM
2. Access corporate data in managed apps
3. Trigger selective wipe from Intune portal
4. Verify corporate data removed, personal data intact
# Verify offline grace period
1. Access managed app while connected
2. Disconnect from network
3. After grace period expires, verify app access blocked
```
### Step 6: Monitor and Respond
Configure MAM monitoring dashboards:
- App protection policy assignment status
- Non-compliant device/user reports
- Selective wipe execution logs
- Jailbreak/root detection alerts
- Failed PIN attempt tracking
## Key Concepts
| Term | Definition |
|------|-----------|
| **MAM** | Mobile Application Management - app-level policies without requiring full device enrollment |
| **App Protection Policy** | Set of rules enforcing data protection at the app level (encryption, DLP, access controls) |
| **Selective Wipe** | Removing only corporate data from managed apps while preserving personal data |
| **App Wrapping** | Post-build process applying MAM SDK policies to apps without source code modification |
| **Containerization** | Isolating corporate app data in an encrypted container separate from personal apps |
## Tools & Systems
- **Microsoft Intune**: Cloud-based MAM/MDM platform with app protection policies
- **Intune App SDK**: SDK for integrating MAM controls into custom iOS/Android apps
- **Intune App Wrapping Tool**: Post-compilation tool for applying MAM policies without code changes
- **VMware Workspace ONE**: Alternative MAM platform with app containerization
- **Azure AD Conditional Access**: Policy engine for enforcing MAM enrollment as access condition
## Common Pitfalls
- **SDK version mismatch**: Intune App SDK version must match the policy version. Outdated SDK versions may silently fail to enforce newer policies.
- **iOS managed pasteboard**: iOS enforces paste restrictions through managed pasteboard, which requires the app to opt-in via Intune SDK integration.
- **App wrapping limitations**: Wrapped apps cannot use certain features (push notifications on some platforms). SDK integration is preferred for full functionality.
- **User experience friction**: Overly restrictive policies cause user frustration and shadow IT. Start with Tier 1 and escalate based on data sensitivity.
@@ -0,0 +1,18 @@
# MAM Implementation Report
## Policy Configuration
| Setting | Value | Baseline | Compliant |
|---------|-------|----------|-----------|
| PIN Required | [VALUE] | [EXPECTED] | [YES/NO] |
| Encryption | [VALUE] | [EXPECTED] | [YES/NO] |
| Clipboard Restriction | [VALUE] | [EXPECTED] | [YES/NO] |
| Screenshot Blocked | [VALUE] | [EXPECTED] | [YES/NO] |
| Jailbreak Blocked | [VALUE] | [EXPECTED] | [YES/NO] |
## Managed Applications
| App | Platform | SDK Integrated | Policy Assigned |
|-----|----------|---------------|----------------|
| [APP] | [PLATFORM] | [YES/NO] | [YES/NO] |
## Recommendations
1. [RECOMMENDATION]
@@ -0,0 +1,19 @@
# Standards Reference: Mobile Application Management
## NIST SP 800-124 Rev 2 - Mobile Device Security
- Section 4: Enterprise mobile security technologies (MDM, MAM, MTD)
- Section 5: App vetting and management requirements
## OWASP Mobile Top 10 2024
| ID | Risk | MAM Mitigation |
|----|------|---------------|
| M6 | Inadequate Privacy Controls | Data separation between personal and corporate |
| M8 | Security Misconfiguration | Enforced app configuration policies |
| M9 | Insecure Data Storage | App-level encryption and backup restrictions |
## CIS Controls v8
| Control | MAM Relevance |
|---------|--------------|
| 2.5 | Allowlist authorized mobile software |
| 3.6 | Encrypt data on end-user devices |
| 6.4 | Require MFA for remote access |
@@ -0,0 +1,14 @@
# Workflows: Mobile Application Management
## Workflow 1: MAM Deployment
```
[Define data classification] --> [Create protection tiers] --> [Configure policies]
| |
[Identify managed apps] [App protection policies]
[Integrate Intune SDK] [App configuration policies]
[Conditional access]
|
[Test on pilot devices]
[Validate DLP controls]
[Roll out to users]
```
@@ -0,0 +1,119 @@
#!/usr/bin/env python3
"""
MAM Policy Compliance Checker
Validates Intune App Protection Policy configurations against security baselines.
Usage:
python process.py --policy policy.json [--baseline tier2] [--output report.json]
"""
import argparse
import json
import sys
from datetime import datetime
from pathlib import Path
BASELINE_TIER2 = {
"pin_required": True,
"min_pin_length": 6,
"biometric_enabled": True,
"encrypt_app_data": True,
"screen_capture_blocked": True,
"backup_blocked": True,
"clipboard_restriction": "managedApps",
"jailbreak_blocked": True,
"offline_grace_period_max_minutes": 1440,
"max_pin_retries": 5,
}
BASELINE_TIER3 = {
**BASELINE_TIER2,
"min_pin_length": 8,
"clipboard_restriction": "blocked",
"offline_grace_period_max_minutes": 720,
"save_as_blocked": True,
"printing_blocked": True,
"max_pin_retries": 3,
}
def check_compliance(policy: dict, baseline: dict) -> list:
"""Check policy against baseline requirements."""
findings = []
data = policy.get("dataProtectionSettings", {})
access = policy.get("accessSettings", {})
conditional = policy.get("conditionalLaunchSettings", {})
checks = {
"pin_required": access.get("pinRequired"),
"min_pin_length": access.get("minimumPinLength", 0),
"biometric_enabled": access.get("biometricEnabled"),
"encrypt_app_data": data.get("encryptAppData"),
"screen_capture_blocked": data.get("screenCaptureBlocked"),
"backup_blocked": data.get("backupBlocked"),
"jailbreak_blocked": conditional.get("jailbreakBlocked"),
}
for control, expected in baseline.items():
actual = checks.get(control)
if actual is None:
findings.append({
"control": control,
"status": "MISSING",
"expected": expected,
"actual": None,
"severity": "HIGH",
})
elif isinstance(expected, bool) and actual != expected:
findings.append({
"control": control,
"status": "NON_COMPLIANT",
"expected": expected,
"actual": actual,
"severity": "HIGH",
})
elif isinstance(expected, int) and isinstance(actual, int) and actual < expected:
findings.append({
"control": control,
"status": "BELOW_MINIMUM",
"expected": f">= {expected}",
"actual": actual,
"severity": "MEDIUM",
})
return findings
def main():
parser = argparse.ArgumentParser(description="MAM Policy Compliance Checker")
parser.add_argument("--policy", required=True, help="Policy JSON file")
parser.add_argument("--baseline", choices=["tier2", "tier3"], default="tier2")
parser.add_argument("--output", default="mam_compliance.json")
args = parser.parse_args()
with open(args.policy) as f:
policy = json.load(f)
baseline = BASELINE_TIER3 if args.baseline == "tier3" else BASELINE_TIER2
findings = check_compliance(policy, baseline)
compliant_count = len(baseline) - len(findings)
report = {
"check": {"policy": args.policy, "baseline": args.baseline, "date": datetime.now().isoformat()},
"summary": {
"total_controls": len(baseline),
"compliant": compliant_count,
"non_compliant": len(findings),
},
"findings": findings,
}
with open(args.output, "w") as f:
json.dump(report, f, indent=2)
print(f"[+] Compliance: {compliant_count}/{len(baseline)} controls pass")
print(f"[+] Report saved: {args.output}")
if __name__ == "__main__":
main()