MENU
An organization created a custom application that is being flagged by Cisco Secure Endpoint. The application must be exempt from being flagged. What is the process to meet the requirement?
Suggested Answer: B
Get Premium 300-710 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
To exempt a custom application from being flagged by Cisco Secure Endpoint, the organization must precalculate the hash value of the custom application and add it to the allowed applications list. This process involves creating a hash of the executable file, which uniquely identifies it, and then configuring Cisco Secure Endpoint to recognize this hash as trusted.
Steps:
Calculate the hash value (e.g., SHA-256) of the custom application executable.
In the Cisco Secure Endpoint management console, navigate to the policy configuration.
Add the calculated hash value to the list of allowed applications or exclusions.
Save and deploy the updated policy.
By adding the hash value to the allowed applications, Cisco Secure Endpoint will recognize the custom application as trusted and will no longer flag it.
33 comments · newest first
ZO
Zona
11 months ago
I thought D was the right answer. This is confusing!
JE
Jesus
11 months ago
Option A seems too simple. I’d stick with B for sure.
SO
Solange
11 months ago
Wait, can we really just modify the detection list? Sounds risky!
JU
Juliana
11 months ago
Definitely agree with that! Hashing is essential for security.
AM
Amie
12 months ago
I think option B is the way to go. Hash values are key.
LE
Leslie
12 months ago
I feel like updating the policy after adding it to DFC is important, but I’m not confident about the exact process.
LY
Lynelle
1 year ago
Adding the app to the allowed applications sounds familiar, but I can't remember if it involves just the hash or something else too.
HA
Haydee
1 year ago
I remember something about modifying detection lists, but I can't recall if that's the right approach for exemptions.
VE
Venita
1 year ago
I think we might need to precalculate the hash value for the application, but I'm not entirely sure if that's the only step needed.
JE
Jenelle
1 year ago
This is a good question to test our understanding of Cisco Secure Endpoint configuration. I think the key is to identify the most efficient and effective way to exempt the custom application from detection.
ZO
Zona
1 year ago
I'm a bit confused by the options here. I'm not familiar with some of the terms like "information-store paths" and "DFC 1st." I'll need to do some research to understand those concepts better.
FA
Fairy
1 year ago
Okay, let's see here. I believe the answer is to modify the custom detection list to exclude the custom application. That seems like the most direct approach.
RE
Refugia
1 year ago
Hmm, I'm not entirely sure about this one. I'll need to carefully read through the options and think it through step-by-step.
GA
Gaston
1 year ago
This looks like a straightforward question about exempting a custom application from Cisco Secure Endpoint detection. I think I can handle this one.
LU
Luisa
1 year ago
Assets held for sale shouldn't be classified as non-current, right? I think they fall under current assets according to IFRS guidelines.
RO
Rosamond
2 years ago
I'm going with B. Seems like the most reliable way to handle this without any potential side effects. Although, I do wonder if Cisco Secure Endpoint has a sense of humor...
TE
Tess
2 years ago
User1: I wonder if Cisco Secure Endpoint has a sense of humor though.
AL
Alana
2 years ago
Yeah, I agree. It's better to precalculate the hash value of the custom application.
EL
Elroy
2 years ago
I think B is the best option too. It's a reliable way to handle it.
TH
Theola
2 years ago
Haha, I bet the developer of this custom app is just hoping it doesn't get flagged at all. Maybe they should have named it 'Cisco Approved' instead of 'Custom Application'.
DO
Dorothy
2 years ago
Wait, what's DFC 1st? I've never heard of that before. Option D sounds a bit sketchy to me.
CA
Cary
2 years ago
Georgiana: That makes sense. I'll go with option A then. Thanks for the help!
GE
Georgiana
2 years ago
Kenneth: I think option A is the best choice. Modifying the custom detection list to exclude the custom application seems like the safest bet.
KE
Kenneth
2 years ago
Oh, I see. Thanks for clarifying that. So, what do you think is the best option to exempt the custom application?
DE
Della
2 years ago
DFC 1st stands for Dynamic File Classification 1st. It's a feature in Cisco Secure Endpoint.
CO
Cordelia
2 years ago
Hmm, I'm not sure. But I like the idea of using the information-store paths in option C. It seems like a more proactive approach than just modifying the detection list.
EL
Elbert
2 years ago
I think the answer is B. Precomputing the hash value and adding it to the allowed applications sounds like the most straightforward way to exempt the custom application from being flagged.
GA
Gail
2 years ago
C) Configure the custom application to use the information-store paths.
AL
Alysa
2 years ago
B) Precompute the hash value of the custom application and add it to the allowed applications.
JO
Jolanda
2 years ago
A) Modify the custom detection list to exclude the custom application.
CO
Cordell
2 years ago
I'm not sure, but I think option B) Precalculate the hash value of the custom application and add it to the allowed applications could also work.
TE
Tess
2 years ago
I agree with Avery. That seems like the most logical solution to meet the requirement.
AV
Avery
2 years ago
I think the answer is A) Modify the custom detection list to exclude the custom application.