About seeding the Application Security database
When you sign in to Application Security for the first time, Application Security requires a minimum set of data to process your initial login credentials and to provide basic functionality. Seeding creates the minimum data set for a new database.
Seeding the Application Security database is necessary to maintain a consistent post-installation configuration. This includes the creation of the default Administrator user account, as well as required entities such as issue templates, report definitions, and other default data required to make Application Security operational.
Application Security requires two of the downloaded seed bundles (see Downloading and unpacking Application Security files):
- The issue template seed bundle (
Fortify_Process_Seed_Bundle-2025_Q2_<build>.zip - The report seed bundle (
Fortify_Report_Seed_Bundle-2025_Q2_<build>.zip
You can also install the optional PCI basic bundles Fortify_PCI_SSF_Basic_Seed_Bundle-2025_Q2_<build>.zip and Fortify_PCI_Basic_Seed_Bundle-2025_Q2_<build>.zip ), which add Payment Card Industry process templates and associated reports to the default set of templates and reports.
The seed bundle files are included in the Application Security installation package. After your initial deployment, you can download off-cycle seed bundles from the Application Security Customer Portal under the PREMIUM CONTENT > FORTIFY EXCHANGE. Quarterly security content releases can also include updated seed bundles.
Only load the bundles shipped with a Application Security release into a Application Security instance of that same version (either a fresh install or an older instance upgraded to the current version).
After you finish seeding the database, you can modify any user‑configurable data entities that were created in the seeding process from the Application Security user interface. For more information, see Additional Application Security configuration.
See Also