S F 3 6 5
AI-First Application Security

Your Security Posture
Defines Your Business
Resilience

10 scanner engines. 28 MCP tools. 17 compliance frameworks. 4 AI agents. One unified Security Factor Score that tells you exactly where you stand.

Security Factor Score

87 /100 SECURE
92
Code
85
Supply
78
Runtime
90
Infra

10+

Scanner Engines

28

MCP Tools

17

Compliance Frameworks

4

AI Agents

COMPLETE PLATFORM

Everything You Need to Secure
Your Software Lifecycle

From the first line of code to production. One platform, one score, complete visibility.

5-Layer Architecture

Layer 1: Scanning

SAST, SCA, DAST, IaC, Secrets, Container, API, AI

Layer 2: Consolidation

Scoring, ASPM Correlation, Compliance, xBOM

Layer 3: Intelligence

4 AI Agents, Advanced AI Engine, MCP Server

Layer 4: Visualization

35+ Portal Modules, Mobile App, Reports

Layer 5: SENTINEL

AI Log Intelligence, Anomaly Detection, Alerts

SCANNER ENGINES

10 Security Engines.
One Unified Platform.

SAST

AI-powered static code analysis. 30+ detection rules, multi-language support, CWE/OWASP mapping, Best Fix Location.

SQL Injection XSS SSRF ReDoS
Learn more

SCA

Software Composition Analysis with malicious package detection, CVE/NVD lookup, license compliance (GPL, AGPL), exploitable path analysis, SBOM generation (SPDX/CycloneDX).

NuGet npm pip Maven

Secrets Detection

35+ patterns for API keys, passwords, tokens, private keys, certificates. AWS, Azure, GCP, GitHub, Slack, Stripe, and more. Entropy analysis + regex matching.

AWS Azure GitHub JWT

IaC Security

25+ rules for Terraform, Kubernetes, Docker, CloudFormation, Ansible, Helm. Public buckets, open security groups, privileged containers, hardcoded credentials.

Container Security

Dockerfile and docker-compose analysis. Root user detection, exposed ports, secrets in ENV, base image vulnerabilities, HEALTHCHECK validation.

AI Security

AI Supply Chain Security. Detect prompt injection, model poisoning, insecure deserialization, RAG poisoning, agent hijacking. OWASP LLM Top 10 + MITRE ATLAS mapping.

Prompt Injection Model Security AIBOM
THE SECURITY FACTOR SCORE

One Number. Seven Pillars.
Complete Visibility.

A proprietary 0-100 score that makes security measurable, understandable, and actionable for both developers and executives.

20%
Code Security

SAST findings, vulnerability density, AI code risks

15%
Supply Chain

Dependencies, CVEs, malicious packages, SBOM

15%
Runtime & API

DAST, API exposure, endpoint risks, shadow APIs

15%
Infrastructure

IaC misconfigs, secrets, cloud/container security

15%
Compliance

OWASP, PCI DSS, HIPAA, GDPR, SOC 2, NIST, ISO 27001, MITRE

10%
Proactive Intel

AI correlations, trend analysis, threat hunting

10%
Observability

SENTINEL logs, anomaly detection, incident MTTR

90-100 FORTIFIED 75-89 SECURE 50-74 EXPOSED 25-49 VULNERABLE 0-24 CRITICAL
AGENTIC AI

4 Autonomous AI Security Agents

Not just scanning tools - intelligent AI agents that triage, remediate, advise, and model threats autonomously.

Triage Agent

Prioritizes findings by real-world exploitability and business impact. Not just CVSS - actual risk.

Remediation Agent

Generates production-ready code fixes with confidence scores. Copy-paste remediation.

Security Copilot

Interactive AI chat. Ask about OWASP, CWE, secure coding, compliance. Your personal security expert.

Threat Modeler

STRIDE/DREAD threat models with Mermaid data-flow diagrams. Visual threat analysis.

COMPANION PRODUCT

SENTINEL

AI-Powered Log Intelligence & Observability Platform.
Works standalone or integrated with Security Factor 365.

Log Ingestion

REST API and gRPC. Structured and unstructured logs. Automatic format normalization and security context enrichment.

AI Anomaly Detection

Brute force, credential stuffing, slow attacks, data exfiltration, privilege escalation. Pattern learning, not static rules.

Attack Chain Correlation

Correlate isolated events into attack timelines. Detect multi-phase attacks: Account Takeover, APT, Data Breach attempts.

EDITIONS

Choose Your Security Level

Starter

For small teams getting started

5 Applications

SAST + SCA Engines

Security Factor Score

SBOM Generation

Basic Reports (PDF/CSV)

10 Core Features

Get Started
MOST POPULAR

Professional

For growing security teams

25 Applications

All 10 Scanner Engines

AI Copilot + Triage + Remediation

Compliance Hub (17 frameworks)

Threat Modeler (STRIDE/DREAD)

Remediation Kanban + Robot Builder

SF Lab + SBOM + CBOM

22 Features

Request Demo

Enterprise

For large organizations

Unlimited Applications

Everything in Professional

SENTINEL Log Intelligence

MCP Server (28 tools)

White-Label Branding

AIBOM + MLBOM + SARIF Import

MITRE ATT&CK Mapping

Executive View + Security Matrix

30+ Features

Contact Sales

Ready to Secure Your Applications?

Start your free trial today. No credit card required. See your Security Factor Score in minutes.

Start Free Trial

SAST - Static Application Security Testing

AI-Powered Source Code Analysis

What is SAST?

Static Application Security Testing analyzes your source code without executing it to find vulnerabilities early in the development lifecycle. Security Factor 365's SAST engine uses AI-enhanced pattern matching and data-flow analysis to detect issues with minimal false positives.

Detection Capabilities

SQL Injection (CWE-89) Command Injection (CWE-78) XSS - Reflected, Stored, DOM (CWE-79) SSRF (CWE-918) XXE (CWE-611) CSRF (CWE-352) Path Traversal (CWE-22) Weak Cryptography (CWE-327) CORS Misconfiguration (CWE-942) Insecure Cookies (CWE-614) ReDoS (CWE-1333) Sensitive Data in Logs (CWE-532)

Supported Languages

C#, Java, Python, JavaScript, TypeScript, PHP, Go, Rust, Kotlin, Swift, Ruby, C/C++, Scala, JSX/TSX, Vue, Razor

Key Differentiators

How Our SAST Engine Works

Unlike simple regex-based scanners, Security Factor 365's SAST engine combines three layers of analysis:

  1. Pattern Matching — 30+ hand-tuned detection rules mapped to CWE identifiers and OWASP categories. Each rule includes severity, vulnerability type, and remediation guidance.
  2. Data-Flow Analysis — Traces user input from source (HTTP request, form data) to sink (SQL query, command execution, HTML output) to detect injection vulnerabilities that span multiple files.
  3. AI Enhancement — Our AI Remediation Agent analyzes each finding in context, generates specific code fixes, and assigns a confidence score so your team knows which fixes to trust immediately.

Example: SQL Injection Detection

VULNERABLE CODE

var query = "SELECT * FROM Users WHERE Id = " + userId;
var cmd = new SqlCommand(query, connection);

SECURE CODE (AI-Generated Fix)

var query = "SELECT * FROM Users WHERE Id = @Id";
var cmd = new SqlCommand(query, connection);
cmd.Parameters.AddWithValue("@Id", userId);

OWASP Top 10 Coverage

OWASP CategoryCWEs DetectedRules
A01 Broken Access ControlCWE-862, CWE-8633
A02 Cryptographic FailuresCWE-327, CWE-328, CWE-321, CWE-3305
A03 InjectionCWE-89, CWE-78, CWE-79, CWE-90, CWE-9188
A05 Security MisconfigurationCWE-489, CWE-209, CWE-942, CWE-6145
A06 Vulnerable ComponentsCWE-3261
A07 Auth FailuresCWE-7981
A09 Logging FailuresCWE-5321
A10 SSRFCWE-9181

ASPM Correlation: When our SAST engine finds an SQL Injection and our Config scanner finds a database password in appsettings.json, the Correlation Engine flags this as a Critical Attack Chain — a compound vulnerability that neither scanner would catch alone. This is what separates Security Factor 365 from basic scanners.

SCA - Software Composition Analysis

Supply Chain Security & Dependency Analysis

What is SCA?

Software Composition Analysis identifies security vulnerabilities, malicious code, and license risks in open-source and third-party dependencies. Our engine scans package manifests, detects transitive dependencies, and cross-references the CVE/NVD databases.

Package Ecosystems

NuGet (.NET) npm (Node.js) pip / PyPI (Python) Maven / Gradle (Java) Go Modules Cargo (Rust)

Key Capabilities

Secrets Detection Engine

35+ Patterns for API Keys, Passwords, Tokens & Credentials

Why Secrets Detection?

Hardcoded secrets in source code are one of the most common and dangerous vulnerabilities. A single exposed API key can lead to full account compromise, data breaches, and financial loss. Our engine continuously scans your codebase for 35+ secret patterns.

Detected Secret Types

AWS Access Keys Azure AD Secrets Google Cloud API Keys GitHub / GitLab Tokens Private Keys (RSA, SSH, PGP) Slack / Twilio / Stripe Tokens Database Connection Strings JWT Secrets npm / NuGet / Docker Tokens Hardcoded Passwords Bearer Tokens

Detection Methods

IaC Security Scanner

Infrastructure-as-Code Misconfiguration Detection

What is IaC Security?

Infrastructure-as-Code security scanning detects misconfigurations before deployment. Catch public S3 buckets, open security groups, privileged containers, and hardcoded credentials in your Terraform, Kubernetes, Docker, and Ansible files.

Supported Platforms

Terraform (HCL) Kubernetes (YAML) Docker / Dockerfile AWS CloudFormation Ansible Playbooks Helm Charts

25+ Detection Rules

The Security Factor Score

Proprietary 7-Pillar Security Health Index (0-100)

How It Works

The Security Factor Score is a weighted composite of 7 security pillars, each measuring a critical dimension of your application's security posture. The score makes security measurable, understandable, and actionable for both developers and executives.

PillarWeightWhat It Measures
Code Security20%SAST findings, vulnerability density, AI code risks
Supply Chain15%Dependency CVEs, malicious packages, license risks, SBOM
Runtime & API15%DAST findings, API exposure, shadow/zombie APIs
Infrastructure15%IaC misconfigs, secrets in code, cloud/container security
Compliance15%OWASP, PCI DSS, HIPAA, GDPR, SOC 2, ISO 27001, NIST
Proactive Intel10%AI trend analysis, threat hunting, attack prediction
Observability10%SENTINEL log intelligence, anomaly detection, MTTR

Score Classifications

90-100 FORTIFIED — Excellent security posture
75-89 SECURE — Good shape, minor improvements
50-74 EXPOSED — Needs attention, moderate risk
25-49 VULNERABLE — Significant issues
0-24 CRITICAL — Immediate action required

Why a Unified Score Matters

Most security tools give you a list of findings. Security Factor 365 gives you a number. That number tells you exactly where you stand, how you compare to your other applications, and whether you're improving or regressing over time.

Scoring Methodology

Each pillar starts at 100 and loses points based on the severity and quantity of findings:

Finding SeverityPoints DeductedExample
Critical-20 per findingSQL Injection, Exposed Private Key
High-10 per findingXSS, Weak Encryption, Open S3 Bucket
Medium-4 per findingCORS Wildcard, Debug Mode, Insecure Cookie
Low-1.5 per findingDeprecated Package, Missing HEALTHCHECK
Info-0.3 per findingHardcoded Role Check, ADD vs COPY

Score Tracking Over Time

Every scan saves a score snapshot. The portal shows trend lines, historical comparisons, and delta indicators so you can see the impact of each sprint on your security posture. The Security Matrix view shows all applications x all 7 pillars in a NASA-style grid for instant portfolio visibility.

Executive View: The CISO dashboard shows fleet-wide Security Factor Score with gauges, KPI cards, compliance status across all 17 frameworks, and AI-generated quick wins. Perfect for board presentations and audit reviews.

Multi-Framework Compliance

17 Security & Compliance Frameworks

Supported Frameworks

OWASP Top 10

Web application security risks. A01-A10 mapped to findings.

OWASP API Top 10

API-specific security risks. BOLA, broken auth, SSRF.

PCI DSS v4.0

Payment card industry. Code review, vulnerability management.

HIPAA

Healthcare data. ePHI protection, encryption, audit controls.

GDPR

EU data protection. Privacy by design, data minimization.

SOC 2 Type II

Trust service criteria. Security, availability, confidentiality.

ISO 27001:2022

Information security management systems standard.

NIST 800-53 / CSF 2.0

Federal security controls. Identify, Protect, Detect, Respond, Recover.

MITRE ATT&CK

Adversary tactics and techniques. Finding-to-tactic mapping.

CWE/SANS Top 25

Most dangerous software weaknesses.

Also supports: FISMA, SLSA, CIS Benchmarks, CCPA, FINRA, FedRAMP, SAMATE

4 Autonomous AI Security Agents

Agentic AI — Not tools, intelligent agents that think, prioritize, and act

Why Agentic AI?

Traditional security tools generate reports. Our AI agents understand context, prioritize by business impact, generate fixes, and learn from your codebase. They work autonomously within your workflow — not as a post-scan afterthought, but as active participants in your security process.

Triage Agent

Prioritizes findings by real-world exploitability, not just CVSS score. Combines heuristic scoring with AI analysis to identify what attackers would actually exploit first.

  • Exploitability scoring — Weighs severity + reachability + exposure + business criticality into a single aggregated risk score (0-100)
  • Context-aware — An SQL injection on a public API is more urgent than one in an internal admin tool. The Triage Agent knows the difference
  • False positive identification — Flags findings likely to be false positives based on code context, reducing noise by up to 60%
  • Batch recommendations — Groups related findings for efficient remediation sprints
  • Integrates with ASPM Correlation Engine — Cross-references SAST+SCA+DAST findings to determine compound exploitability
Remediation Agent

Generates production-ready code fixes with confidence scoring. Not generic advice — actual code you can copy-paste into your codebase.

  • Language-specific fixes — Generates remediation in C#, Java, Python, JavaScript, Go, PHP, and more
  • Before/after comparison — Shows the vulnerable code alongside the corrected version
  • Confidence scoring — Each fix carries a High/Medium/Low confidence level so you know when to review manually
  • Best Fix Location — Identifies the root cause point where a single fix resolves multiple related findings
  • Auto-creates Kanban tasks — Generates remediation tasks with effort estimates (Quick Fix, Hours, Days, Sprint)
Security Copilot

Your personal security expert, available 24/7. An interactive AI assistant that understands your application context and answers security questions in real-time.

  • "Explain this vulnerability" — Breaks down any CWE or finding in plain language with business impact
  • "How do I fix this?" — Provides step-by-step remediation guidance with code
  • "Are we PCI DSS compliant?" — Answers compliance questions against your actual scan data
  • "What should we prioritize this sprint?" — Recommends the highest-impact security improvements
  • Multi-turn conversations — Remembers context across a session for deep-dive analysis
  • Works on every page — Available as a floating assistant throughout the portal
Threat Model Agent

AI-assisted threat modeling that transforms application descriptions into structured threat analyses with visual diagrams.

  • STRIDE analysis — Systematic evaluation of Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege threats
  • DREAD scoring — Ranks threats by Damage potential, Reproducibility, Exploitability, Affected users, and Discoverability
  • Data-flow diagrams — Generates visual Mermaid diagrams showing trust boundaries, data flows, and entry points
  • Prioritized threat table — Ranked by risk with recommended mitigations for each threat
  • Component-level analysis — Drill into specific APIs, services, or modules for focused threat assessment
  • Export as documentation — Generate compliance-ready threat model documents

How It All Connects

The four agents work together as a pipeline: the Triage Agent prioritizes what matters, the Remediation Agent generates fixes, the Copilot answers questions along the way, and the Threat Modeler provides the strategic view. All powered by the same AI engine, all sharing context about your application.

Pro Tip: Combine AI Triage with ASPM Correlation Engine results. When the Triage Agent scores a correlated finding (one found by multiple engines), its priority automatically increases because cross-engine validation confirms exploitability.

AI Security Scanning

AI Supply Chain, LLM Vulnerability & Model Security Analysis

Why AI Security Scanning?

Traditional application security tools were built for a world without AI. They scan for SQL injection, XSS, and dependency vulnerabilities — but miss an entirely new class of threats introduced by LLMs, ML models, AI agents, and vector databases. Security Factor 365 is the first platform to include a dedicated AI Security scanner alongside traditional AppSec engines.

12 Detection Rules

Prompt Injection (LLM01) Insecure Model Loading (CWE-502) AI API Key Exposure (CWE-798) Unvalidated LLM Output (LLM02) LLM Output as Code (CWE-95) Unsafe Model Download (LLM05) RAG Data Injection (CWE-20) Agent Over-Permission (LLM08) Training Data PII (CWE-359) Exposed Model Artifacts (CWE-538) Missing AI Input Validation Insecure AI Configuration

AI Asset Discovery

While scanning, the engine automatically discovers and inventories all AI components in your codebase:

LLM Integrations

OpenAI, Anthropic, Cohere, Replicate, HuggingFace model imports and API calls.

Agent Frameworks

LangChain, AutoGen, CrewAI, custom agent implementations with tool execution.

MCP Servers

Model Context Protocol server implementations and tool registrations.

Vector Stores

FAISS, Chroma, Pinecone, Weaviate, Qdrant — RAG infrastructure discovery.

Prompt Templates

System prompts, chat templates, and prompt engineering patterns.

Model Artifacts

.h5, .pkl, .pt, .onnx, .safetensors files — model storage and deployment paths.

Example: Prompt Injection Detection

VULNERABLE CODE

prompt = f"You are a helpful assistant. Answer this: {user_input}"
response = openai.ChatCompletion.create(
    model="gpt-4", messages=[{"role": "user", "content": prompt}]
)

SECURE CODE

system_prompt = "You are a helpful assistant. Only answer factual questions."
sanitized_input = sanitize_user_input(user_input, max_length=500)
response = openai.ChatCompletion.create(
    model="gpt-4",
    messages=[
        {"role": "system", "content": system_prompt},
        {"role": "user", "content": sanitized_input}
    ],
    max_tokens=1000,
    temperature=0.7
)

Compliance Mapping

FrameworkCoverageCategories
OWASP LLM Top 1010/10LLM01-LLM10
MITRE ATLAS12 tacticsAML.TA0001-TA0012
EU AI ActArt. 9, 10, 15High-risk system requirements
ISO 42001Clause 6, 8AI risk assessment & controls
NIST AI RMFGovern, Map, Measure, ManageAI risk functions
CSA MAESTROAll 7 layersMulti-agent security

ASPM Correlation: When our AI Security scanner finds a prompt injection vulnerability and our Secrets scanner finds an exposed OpenAI API key in the same project, the Correlation Engine flags this as a Critical AI Attack Chain — an attacker could use the exposed key to exploit the injection point. This compound risk is invisible to traditional scanners.

DAST — Dynamic Application Security Testing

Runtime Vulnerability Discovery & API Fuzzing

What is DAST?

Dynamic Application Security Testing analyzes running applications from the outside — just like an attacker would. Unlike SAST (which reads source code), DAST sends actual HTTP requests, fuzzes inputs, and observes responses to find vulnerabilities that only manifest at runtime.

How SF365 DAST Works

Intelligent Crawling

Automatically discovers endpoints, forms, APIs, and hidden parameters. Maps the full attack surface before testing.

Injection Fuzzing

Tests for SQL injection, XSS, command injection, SSRF, and LDAP injection using thousands of attack payloads.

Authentication Testing

Tests session management, cookie security, CSRF protection, brute force resistance, and MFA bypass attempts.

API Security Testing

OWASP API Top 10 coverage. Tests REST, GraphQL, and gRPC endpoints for BOLA, broken auth, mass assignment.

Header & Config Analysis

Validates security headers (CSP, HSTS, X-Frame-Options), TLS configuration, CORS policies, and server information leaks.

Business Logic Testing

Detects rate limiting gaps, privilege escalation paths, insecure direct object references, and workflow bypass opportunities.

DAST + SAST = ASPM Correlation

When DAST confirms a vulnerability that SAST also found in source code, the ASPM Correlation Engine elevates its priority — a finding validated by two engines is far more likely to be a real, exploitable issue. This dramatically reduces false positives.

Cross-Engine Validation: A SQL injection found by SAST in source code AND confirmed by DAST at runtime gets a correlated risk score up to 2x higher — because it's proven exploitable.

Container Security

Docker, Kubernetes & Cloud-Native Security

What is Container Security?

Container security covers the entire lifecycle of containerized applications — from base image selection through build-time scanning to runtime monitoring. As organizations adopt Docker and Kubernetes, the attack surface expands with misconfigured containers, vulnerable images, and overprivileged workloads.

What SF365 Scans

Image Vulnerability Scanning

Scans Docker images for known CVEs in OS packages and application dependencies. Checks against NVD, GitHub Advisory, and vendor databases.

Dockerfile Best Practices

Detects running as root, unnecessary packages, missing health checks, exposed secrets in build args, and multi-stage build opportunities.

Kubernetes Misconfigurations

Validates Pod Security Standards, RBAC policies, network policies, resource limits, and secret management in K8s manifests.

Registry Security

Verifies image signing, provenance attestation, tag immutability, and pull policies. Ensures only trusted images reach production.

Runtime Behavior

Monitors container behavior for anomalies: unexpected network connections, file system modifications, privilege escalation attempts.

CBOM Generation

Generates Container Bill of Materials — a full inventory of every package, library, and binary inside your container images.

Pro Tip: Integrate container scanning in your CI/CD pipeline. SF365 can fail builds that use images with critical CVEs or that run as root — catching issues before they reach production.

SENTINEL — AI Log Intelligence

Real-Time Anomaly Detection & Attack Chain Correlation

What is SENTINEL?

SENTINEL is Security Factor 365's companion product for AI-powered log intelligence. It works standalone or fully integrated with SF365, providing real-time anomaly detection, attack chain correlation, and intelligent alerting that goes far beyond traditional SIEM rule matching.

Core Capabilities

Log Ingestion

REST API and gRPC endpoints ingest logs from any source — application logs, web servers, firewalls, cloud providers, databases, and custom sources.

Normalization Engine

Normalizes diverse log formats into a unified schema with automatic enrichment — geo-IP, threat intelligence, application context, user identity.

AI Anomaly Detection

Machine learning models detect brute force, credential stuffing, data exfiltration, privilege escalation, and slow/low attacks that rule-based systems miss.

Attack Chain Correlation

Connects related events across time and sources to reconstruct full attack timelines. Classifies attack chains by MITRE ATT&CK tactics.

Behavior-Based Alerts

Alerts based on behavioral baselines, not static rules. Detects deviations from normal patterns — new access patterns, unusual data volumes, off-hours activity.

Log Explorer & Dashboard

Full-text search, filtering, timeline visualization, and drill-down analysis. Real-time streaming view for active incident response.

Attack Types Detected

SENTINEL + SF365: When SENTINEL detects an attack targeting a vulnerability that SF365 already found in your code, it automatically escalates both the finding and the alert — closing the loop between AppSec and runtime security.

Offline Audit Mode

Security Log Audit as a Service — No agents, no installation, no access to client systems required. Simply upload log files and SENTINEL does the rest.

Upload & Analyze

Upload .log, .json, .csv, .txt, IIS W3C, Apache, nginx, syslog files. Auto-format detection.

Full AI Pipeline

Every file goes through: Ingestion → Normalization → AI Analysis → Correlation → Report.

Attack Chain Detection

Cross-file correlation detects multi-phase attacks: reconnaissance → brute force → escalation → exfiltration.

Audit Report

Export PDF/CSV reports with anomalies, attack chains, severity breakdown, top source IPs, and recommendations.

Perfect for Consultants & MSSPs: Offer security log auditing to your clients without deploying any software. Upload their logs, generate AI-powered findings, and deliver a professional audit report — all from the SENTINEL portal.

MCP Server — Model Context Protocol

28 AI Tools for Security Automation

What is MCP?

The Model Context Protocol (MCP) server exposes SF365's entire security platform as 28 AI-callable tools. This means AI assistants like Claude, GPT, or custom agents can directly trigger scans, query findings, generate reports, and manage remediations — all through a standardized protocol.

28 Tools in 8 Categories

Scanning (4 tools)

RunSastScan, RunScaScan, RunDastScan, RunFullScan — trigger any scan type programmatically.

Analysis (4 tools)

GetSecurityScore, GetFindings, GetFindingDetail, AnalyzeCode — query security data and analyze code snippets.

Discovery (3 tools)

ListApplications, GetAppDetail, GetDependencyTree — explore the application portfolio.

Compliance (3 tools)

GetComplianceStatus, GetComplianceGaps, MapToFramework — audit compliance against any framework.

Reporting (3 tools)

GenerateReport, GetSbom, ExportFindings — create PDF/CSV reports and SBOM documents.

Remediation (3 tools)

SuggestFix, GetRemediationPlan, PrioritizeFindings — AI-powered fix generation and prioritization.

SENTINEL (3 tools)

QueryLogs, GetAnomalies, GetAlerts — interact with log intelligence and anomaly detection.

System (5 tools)

HealthCheck, TestConnection, GetScanHistory, GetPlatformStats, ValidateLicense — system management.

AI-Native Security: Connect SF365 MCP to Claude Code, VS Code Copilot, or any MCP-compatible AI — your security platform becomes part of the developer's natural workflow.

xBOM — Extended Bill of Materials

SBOM, CBOM, MLBOM & AIBOM

Beyond SBOM — The xBOM Family

Modern applications aren't just code and libraries. They include containers, ML models, AI components, and infrastructure. SF365 generates a complete inventory across all dimensions:

SBOM — Software BOM

Complete inventory of all software components, libraries, and dependencies. Supports SPDX 2.3 and CycloneDX 1.5 formats. Required by US Executive Order 14028.

CBOM — Container BOM

Full inventory of every package, binary, and library inside container images. Tracks base image lineage and layer-by-layer composition.

MLBOM — ML Model BOM

Documents ML model dependencies, training data sources, framework versions, and model provenance for AI governance and compliance.

AIBOM — AI Asset BOM

Inventories AI components: LLM integrations, prompt templates, vector stores, fine-tuned models, and AI pipeline dependencies.

Why xBOM Matters

Auto-Generated: SF365 generates xBOM documents automatically during scans — no manual inventory required. Export in SPDX or CycloneDX format for regulatory submissions.

OWASP Top 10

The Most Critical Web Application Security Risks

What is OWASP?

The Open Worldwide Application Security Project (OWASP) is a nonprofit foundation dedicated to improving the security of software. The OWASP Top 10 is the most widely recognized standard for web application security awareness, updated periodically based on real-world vulnerability data from hundreds of organizations.

OWASP Top 10 — 2021 Edition

A01: Broken Access Control

94% of apps tested had some form of broken access control. Users acting outside their intended permissions.

A02: Cryptographic Failures

Failures related to cryptography that lead to exposure of sensitive data — weak algorithms, missing encryption, improper key management.

A03: Injection

SQL, NoSQL, OS, LDAP injection. User-supplied data sent to an interpreter as part of a command or query without validation.

A04: Insecure Design

Missing or ineffective security controls in the design phase. Threat modeling and secure design patterns are needed.

A05: Security Misconfiguration

Default configs, open cloud storage, unnecessary features enabled, verbose error messages, missing security headers.

A06: Vulnerable Components

Using components with known vulnerabilities. Libraries, frameworks, and other software modules running with the same privileges.

A07: Auth Failures

Weak authentication mechanisms — credential stuffing, brute force, weak passwords, missing MFA, improper session management.

A08: Software & Data Integrity

Assumptions about software updates, critical data, and CI/CD pipelines without verifying integrity. Deserialization attacks.

A09: Logging & Monitoring Failures

Insufficient logging, detection, monitoring, and active response. Breaches take 200+ days to detect without proper monitoring.

A10: SSRF

Server-Side Request Forgery occurs when a web app fetches a remote resource without validating the user-supplied URL.

How SF365 Maps to OWASP

Every finding detected by our SAST, SCA, DAST, and IaC engines is automatically mapped to the relevant OWASP category. The Compliance Hub shows your coverage percentage for each A01-A10 category, identifies gaps, and tracks remediation progress over time.

Real-Time Compliance: Your OWASP compliance score updates in real-time after every scan. No more manual mapping spreadsheets — SF365 does it automatically across all 10 categories.

PCI DSS v4.0

Payment Card Industry Data Security Standard

What is PCI DSS?

The Payment Card Industry Data Security Standard (PCI DSS) is a set of security standards designed to ensure that all companies that accept, process, store, or transmit credit card information maintain a secure environment. Version 4.0 (effective March 2024) introduces significant new requirements for application security.

Key Requirements for AppSec

Req 6.2: Bespoke Software

Software developed securely using secure coding practices. Vulnerability identification and remediation processes.

Req 6.3: Vulnerability Management

Known vulnerabilities identified and managed. CVE tracking, dependency scanning, timely patching.

Req 6.4: Public Web Apps

Public-facing web applications protected against attacks. WAF deployment or automated vulnerability assessment.

Req 6.5: Change Management

All changes documented, tested, and approved. Security impact assessed for every code change.

Req 11.3: Pen Testing

Regular penetration testing. Internal and external, application-layer testing including injection and auth flaws.

Req 11.4: Intrusion Detection

Network and application-level intrusion detection. Real-time monitoring and alerting on suspicious activity.

What Changed in v4.0

SF365 Compliance: Our SAST and SCA engines satisfy Requirement 6.2.4 (automated code review) and 6.3.2 (vulnerability management). The Compliance Hub generates PCI DSS-ready audit reports with evidence mapping.

HIPAA

Health Insurance Portability and Accountability Act

What is HIPAA?

HIPAA is a US federal law that mandates the protection of sensitive patient health information (PHI/ePHI). Any organization that handles electronic Protected Health Information must implement administrative, physical, and technical safeguards to ensure confidentiality, integrity, and availability.

Security Rule — Technical Safeguards

§164.312(a): Access Control

Unique user identification, emergency access, automatic logoff, encryption/decryption of ePHI at rest.

§164.312(b): Audit Controls

Hardware, software, and procedural mechanisms to record and examine access to ePHI systems.

§164.312(c): Integrity Controls

Policies and procedures to protect ePHI from improper alteration or destruction. Data validation mechanisms.

§164.312(d): Authentication

Verify that a person seeking access to ePHI is who they claim to be. Strong authentication mechanisms.

§164.312(e): Transmission Security

Technical measures to guard against unauthorized access to ePHI transmitted over electronic networks. TLS/encryption.

Breach Notification Rule

Must notify affected individuals, HHS, and media (500+ records) within 60 days of discovering a breach.

Why AppSec Matters for HIPAA

Application vulnerabilities are the #1 vector for healthcare data breaches. SQL injection, broken authentication, and misconfigured APIs can expose millions of patient records. HIPAA violations carry penalties up to $1.5 million per violation category per year.

SF365 for Healthcare: Our Secrets Scanner detects hardcoded ePHI, API keys, and connection strings. SAST finds authentication and encryption weaknesses. The Compliance Hub maps every finding to specific HIPAA sections.

GDPR

General Data Protection Regulation (EU)

What is GDPR?

The General Data Protection Regulation is the EU's comprehensive data privacy law, effective since May 2018. It governs how organizations collect, process, store, and protect personal data of EU residents. Non-compliance can result in fines up to €20 million or 4% of global annual turnover.

Key Principles for Application Security

Art. 25: Privacy by Design

Data protection must be integrated into processing activities from the design stage. Security controls built in, not bolted on.

Art. 32: Security of Processing

Implement appropriate technical measures: pseudonymization, encryption, confidentiality, integrity, availability, and resilience.

Art. 33: Breach Notification

Report breaches to supervisory authority within 72 hours. Notification must describe nature, consequences, and measures taken.

Art. 35: DPIA

Data Protection Impact Assessment required for high-risk processing. Systematic description, necessity assessment, risk evaluation.

Art. 5: Data Minimization

Personal data must be adequate, relevant, and limited to what is necessary. Applications must not collect excessive data.

Art. 17: Right to Erasure

Users have the right to be forgotten. Applications must support complete data deletion when requested.

Application Security & GDPR

GDPR doesn't prescribe specific technologies but requires "appropriate technical measures." This means vulnerability management, encryption validation, access control testing, and logging are all implicitly required. A data breach caused by a known, unpatched vulnerability is a clear compliance failure.

SF365 for GDPR: Our scanners detect personal data exposure, insecure data storage, missing encryption, and logging gaps. The Compliance Hub shows your GDPR readiness across all articles and generates audit-ready documentation.

SOC 2 Type II

Service Organization Control — Trust Service Criteria

What is SOC 2?

SOC 2 is an auditing standard developed by the AICPA for service organizations. It evaluates an organization's information systems against five Trust Service Criteria (TSC). Type II reports cover a period of time (typically 6-12 months) and verify that controls are not only designed but also operating effectively.

Five Trust Service Criteria

CC: Security (Common Criteria)

Protection against unauthorized access. Firewalls, intrusion detection, MFA, vulnerability management, security monitoring.

A: Availability

System availability for operation and use as committed. Performance monitoring, disaster recovery, incident handling.

PI: Processing Integrity

System processing is complete, valid, accurate, timely, and authorized. Data validation, error handling, QA processes.

C: Confidentiality

Information designated as confidential is protected as committed. Encryption, access controls, data classification.

P: Privacy

Personal information collected, used, retained, and disclosed conforms to commitments. Notice, consent, access rights.

Key Controls for Application Security

SF365 for SOC 2: Continuous vulnerability scanning satisfies CC6.1 and CC7.1. Our audit trail covers CC8.1 change management. The Compliance Hub provides evidence mapping for your SOC 2 auditor.

NIST Framework

NIST 800-53 & Cybersecurity Framework (CSF) 2.0

What is NIST?

The National Institute of Standards and Technology (NIST) publishes cybersecurity frameworks used globally. NIST SP 800-53 provides a catalog of security and privacy controls, while the Cybersecurity Framework (CSF) 2.0 (released February 2024) provides a voluntary framework for managing cybersecurity risk.

CSF 2.0 — Six Core Functions

GOVERN (New in 2.0)

Establish and monitor cybersecurity risk management strategy, expectations, and policy. Organizational context and supply chain risk.

IDENTIFY

Understand assets, business environment, governance, risk assessment, and supply chain. Asset management and risk strategies.

PROTECT

Develop and implement safeguards. Access control, awareness training, data security, protective technology, maintenance.

DETECT

Develop and implement activities to identify cybersecurity events. Continuous monitoring, anomaly detection, security events.

RESPOND

Take action regarding detected cybersecurity incidents. Response planning, communications, analysis, mitigation, improvements.

RECOVER

Maintain resilience plans and restore capabilities impaired by cybersecurity incidents. Recovery planning, improvements, comms.

NIST 800-53 Key Control Families

SF365 for NIST: Our platform maps findings to NIST 800-53 controls (SA-11, SI-2, SI-5, RA-5) and CSF 2.0 subcategories. SENTINEL covers the DETECT function. The Compliance Hub generates NIST-ready assessment reports.