# SAST

Static Application Security Testing (SAST) is a method for finding security vulnerabilities in application software program code before they are implemented. In SAST, analysis is performed statically on the program code without actively running the application. This method examines the code in depth for flaws and vulnerabilities that could be exploited by unauthorized parties. By using SAST, you can detect security problems as early as possible, fix them, and reduce the risk of attacks on the resulting applications. SAST assists in increasing the reliability and security of application software before deployment to production environments.

\
To review the results of a scanned project. On the Cloudeka services portal page click the Overview menu. On the Overview page of SAST there is a summary of the information.

<figure><img src="https://putri.box.cloudeka.id/cloudeka-assets/static/images/19dekaast/4.0.overview.png" alt=""><figcaption><p>SAST</p></figcaption></figure>

<table><thead><tr><th width="233">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>(a) Overall Code</strong></td><td>Displays the state based on the entire scanned code.</td></tr><tr><td><strong>(b) New Code</strong></td><td>Displays a brief description based on the newly scanned code.</td></tr><tr><td><strong>(c) Reability</strong></td><td>Displays a problem if there is a bug in the code that has been implemented.</td></tr><tr><td><strong>(d) Bug</strong></td><td>Shows the total number of bugs found at the time the code is scanned.</td></tr><tr><td><strong>(e) Security</strong></td><td>Security on security applications.</td></tr><tr><td><strong>(f) Vulnerabilities</strong></td><td>Problems related to finding kdependency in applied code.</td></tr><tr><td><strong>(g) Maintainability</strong></td><td>The ease and effectiveness of maintaining a software application throughout lifecycle.</td></tr><tr><td><strong>(h) Code Smells</strong></td><td>Displays an indication of a problem that could potentially reduce the quality of code.</td></tr><tr><td><strong>(i) Effort to fix</strong></td><td>Displays the estimated time it takes to fix all problems.</td></tr><tr><td><strong>(j) Security Review</strong></td><td>Shows the results of identifying the check process to the checkpointthe right thing to do.</td></tr><tr><td><strong>(k) Security Detector</strong></td><td>To detect potential vulnerabilities in security.</td></tr><tr><td><strong>(l) Security Reviewed</strong></td><td>Percentage is associated with the number of corrected problems.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.id/security/deka-ast/sast.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.