Skip to content

Commit b5084cc

Browse files
committed
move beta ntoe
1 parent 6f87b1d commit b5084cc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/codeql/codeql-language-guides/customizing-library-models-for-java-and-kotlin.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ You can model the methods and callables that control data flow in any framework
99

1010
.. include:: ../reusables/beta-note-model-packs-java.rst
1111

12+
.. include:: ../reusables/beta-note-threat-models-java.rst
13+
1214
About this article
1315
------------------
1416

@@ -297,8 +299,6 @@ The first four values identify the callable (in this case a method) to be modele
297299
Threat models
298300
-------------
299301

300-
.. include:: ../reusables/beta-note-model-packs-java.rst
301-
302302
A threat model is a named class of dataflow sources that can be enabled or disabled independently. Threat models allow you to control the set of dataflow sources that you want to consider unsafe. For example, one codebase may only consider remote HTTP requests to be tainted, whereas another may also consider data from local files to be unsafe. You can use threat models to ensure that the relevant taint sources are used in a CodeQL analysis.
303303

304304
The ``kind`` property of the ``sourceModel`` determines which threat model a source is associated with. There are two main categories:

0 commit comments

Comments
 (0)