Skip to content

armgit / AiSOC

Public Imported from GitHub
0

Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.

2.2 KB
Raw Blame
id: aws-vpc-flow
name: AWS VPC Flow Logs
version: 1.0.0
category: cloud
vendor: Amazon Web Services
publisher: AiSOC Community
description: >
  Streams AWS VPC Flow Log records from CloudWatch Logs with a default
  REJECT-only filter pattern so detections see denied connections (port
  scans, brute-force attempts, exfiltration probes) without paying to
  ingest the steady-state ACCEPT firehose. Parses the default v2
  fixed-column layout natively and passes v5 / JSON custom layouts
  through on raw_event for downstream rules.
homepage: https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html
docs_url: /docs/connectors/aws-vpc-flow
license: MIT
capabilities:
  - pull_alerts
  - pull_logs
config_schema:
  - name: region
    label: AWS Region
    type: string
    required: true
    default: us-east-1
    help_text: AWS region the CloudWatch Logs group lives in.
  - name: log_group_name
    label: CloudWatch Logs log group
    type: string
    required: true
    help_text: >
      The CloudWatch Logs log group your VPC Flow Logs publish to
      (e.g. ``/aws/vpc/flowlogs``). Configure the flow log to publish
      to CloudWatch Logs in the VPC console first if you haven't.
  - name: filter_pattern
    label: CloudWatch Logs filter pattern
    type: string
    required: false
    default: "?REJECT"
    help_text: >
      CloudWatch Logs filter pattern applied server-side. Default
      ``?REJECT`` surfaces blocked flows only. Set to empty string to
      ingest every flow record (high volume warning).
  - name: flow_log_version
    label: Flow log version (v2 or v5)
    type: string
    required: false
    default: v2
    help_text: >
      AiSOC parses v2 (the AWS default 14-field layout) natively. For
      v5 custom layouts the raw record passes through on raw_event so
      detection content can match on the JSON.
  - name: access_key
    label: Access Key ID
    type: string
    required: false
    help_text: >
      Leave blank to use the runtime IAM role / instance profile
      (recommended for production deployments).
  - name: secret_key
    label: Secret Access Key
    type: secret
    required: false
    help_text: Required only when supplying a static access key above.