JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.2p0 | CONFIDENTIAL | CodeSecure Inc |
At this point you will have done the following (if you have missed any steps, do them now).
This section suggests further setup steps that you may wish to perform, and provides links to introductory material on using CodeSonar.
If you are responsible for running a hub, there are some
additional details to consider before you start using it.
(If you are using a SaaS hub, it has already been configured to your
organization's specifications.)
The Task: Lock Down a Hub section provides step by step instructions for setting up a hub with security-conscious resolutions for these (and other) questions.
In particular, we strongly recommend that you choose a policy for warning annotation sharing ("warning group scope") early in the hub's lifetime and then keep it unchanged.
You may wish to do some or all of the following at this stage.
If you have upgraded CodeSonar, also do the following.
You may also wish to work through Task: See How Results Have Changed After Upgrading CodeSonar.
We recommend starting with the Basic Tutorial.
Eclipse and Visual Studio users may be interested in the CodeSonar plug-ins for Eclipse and Visual Studio, in which case we also recommend:
To report problems with this documentation, please visit https://support.codesecure.com/.