exam questions

Exam CAS-004 All Questions

View all questions & answers for the CAS-004 exam

Exam CAS-004 topic 1 question 219 discussion

Actual exam question from CompTIA's CAS-004
Question #: 219
Topic #: 1
[All CAS-004 Questions]

An organization is establishing a new software assurance program to vet applications before they are introduced into the production environment. Unfortunately, many of the applications are provided only as compiled binaries. Which of the following should the organization use to analyze these applications? (Choose two.)

  • A. Regression testing
  • B. SAST
  • C. Third-party dependency management
  • D. IDE SAST
  • E. Fuzz testing
  • F. IAST
Show Suggested Answer Hide Answer
Suggested Answer: EF 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
grelaman
8 months ago
Selected Answer: BE
Why not IAST, because you need to access to the original code to integrate it with special libraries and agents to make it works. So, if you have the compiled binaries it won't work. SAST can be used with compiled binaries.
upvoted 2 times
...
Anarckii
1 year, 6 months ago
Selected Answer: EF
E. Fuzz testing Fuzz testing involves providing unexpected or random inputs to compiled binaries to discover vulnerabilities or unexpected behaviors. F. IAST (Interactive Application Security Testing) IAST involves testing an application during runtime, and it can be effective in analyzing the behavior of compiled binaries in real-world scenarios.
upvoted 1 times
Anarckii
1 year, 6 months ago
Changing to BE
upvoted 3 times
...
...
32d799a
1 year, 8 months ago
Selected Answer: BE
Considering the limitations and needs of analyzing compiled binaries, the most appropriate choices from the given list are: B. SAST (with the understanding it would be used on binary code) E. Fuzz testing
upvoted 2 times
...
Ariel235788
1 year, 8 months ago
Selected Answer: BF
To analyze compiled binaries of applications for software assurance, the organization should consider the following approaches: B. SAST (Static Application Security Testing): SAST analyzes the application's source code or binary code without executing it. While it's more commonly used with source code, some SAST tools support binary analysis. SAST can identify potential security vulnerabilities and coding issues within the application, making it a valuable tool for vetting applications for security concerns. F. IAST (Interactive Application Security Testing): IAST tools, sometimes known as hybrid analysis tools, combine elements of both SAST and DAST (Dynamic Application Security Testing). They can analyze running applications (including compiled binaries) to identify security vulnerabilities in real-time. IAST tools can provide insights into the application's behavior during runtime and help pinpoint vulnerabilities within the binaries.
upvoted 4 times
nuel_12
1 year, 7 months ago
if you look at your explanation IAST is hybrid why will you choose SAST when IAST can perform both function, the best choice of answer for a binary code is EF, fuzz test and IAST
upvoted 2 times
...
...
BiteSize
1 year, 11 months ago
Selected Answer: EF
"Code has been compiled already into an application" Fuzz Testing - messing with the application by sending unexpected inputs of data to see the behavior Interactive Application Security Testing (IAST) - Monitors the behavior of the program as it runs - Malware sandbox does this as well. Source: Verifying each answer against Chat GPT, my experience, other test banks, a written book, and weighing in the discussion from all users to create a 100% accurate guide for myself before I take the exam. (It isn't easy because of the time needed, but it is doing my diligence)
upvoted 4 times
...
javier051977
2 years, 2 months ago
Selected Answer: EF
IAST (Interactive Application Security Testing): IAST can be used to analyze the behavior of the running application to identify vulnerabilities, even if the application is provided only as compiled binaries. This can be done by instrumenting the application and monitoring its behavior at runtime, which can help identify potential security issues. Fuzz testing: Fuzz testing is a technique that involves sending large volumes of malformed or unexpected data to an application to see how it responds. This can help identify potential vulnerabilities and weaknesses in the application, even if the source code is not available. By sending a variety of inputs to the compiled binary, fuzz testing can help identify unexpected behaviors and crashes that may be indicative of security issues.
upvoted 3 times
...
Geofab
2 years, 2 months ago
Selected Answer: EF
E and F are correct as they are for testing software that is executing
upvoted 2 times
...
Amin4799
2 years, 2 months ago
Selected Answer: BF
I go to B,F
upvoted 3 times
...
smqzbq
2 years, 3 months ago
Selected Answer: E
I'll go with EF.
upvoted 3 times
...
smqzbq
2 years, 3 months ago
Guys, I wonder how can you any dependency management if you get binaries, so you don't really know what, which version is underneth, or what dependencies other dependencies depend on ;)
upvoted 1 times
...
professorx123
2 years, 3 months ago
the key word here being "compiled binaries" E and F
upvoted 2 times
...
Broesweelies
2 years, 3 months ago
Selected Answer: EF
E and F.
upvoted 4 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...