# Default workflows

Default workflows are provided with product. They are usable directly in App objects by mentioning their name.

# Default

This workflow is the defaut security workflow. It provides protection against web intrusions and you can specify a security exception configuration.

# Example of call in Application

  workflow: Default
  workflow_params:
    exceptions: my-exceptions
1
2
3

# Parameters

  • exceptions: SecurityException
  • icx: ICXConfiguration (always default)

# Context description

This workflow provides security that can be configured according to protected application. It makes securing and false positive handling simple and allows to adapt security to your application Example: if there are no SQL database in your application you don't need to block payload that looks like SQL injections.

# Example of call in Application

  workflow: ContextDescription
  workflow_params:
    app.type: "unknown"
    app.language: "unknown"
    os.type: "unknown"
    sql.db: true
    ldap.connection: true
    email.library: true
    secure.headers: true
    exception.configuration: my-exceptions
1
2
3
4
5
6
7
8
9
10

# Parameters

  • app.type: Type of application
    • Dynamic web pages (dynamic)
    • Static web pages (static)
    • API REST (JSON) (rest)
    • API SOAP (XML) (soap)
    • Hybrid (hybrid)
    • Unknown (unknown)
  • app.language: Language used in application
    • PHP (php)
    • JAVA (java)
    • ASP.NET (asp.net)
    • Javascript (js)
    • HTML (html)
    • Unknown (unknown)
  • os.type: Type of guest OS
    • Unix (unix)
    • Windows (windows)
    • Multiple (multiple)
    • Unknown (unknown)
  • sql.db: Application use SQL (bool)
  • ldap.connection: Application use LDAP (bool)
  • email.library: Application use emails
  • secure.headers: Enable headers security (bool)
  • exception.configuration: SecurityException object
Last Updated: 5/20/2021, 9:59:34 AM