ARMFBTech (Community Member) asked a question.
Maybe the scanner is interpreting the team name or signing cert name as sensitive?
I've attached a sample of the info.plist file and included in inline below.
```plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ApplicationProperties</key>
<dict>
<key>ApplicationPath</key>
<string>Applications/direct.app</string>
<key>Architectures</key>
<array>
<string>arm64</string>
</array>
<key>CFBundleIdentifier</key>
<string>com.companyname.appname.direct.analysis</string>
<key>CFBundleShortVersionString</key>
<string>1.21.1</string>
<key>CFBundleVersion</key>
<string>1.21.1</string>
<key>SigningIdentity</key>
<string>Apple Development: Created via API (B1HJFCZMNB)</string>
<key>Team</key>
<string>E31K19LSV2</string>
</dict>
<key>ArchiveVersion</key>
<integer>2</integer>
<key>CreationDate</key>
<date>2023-03-02T14:52:30Z</date>
<key>Name</key>
<string>direct-prod-analysis</string>
<key>SchemeName</key>
<string>direct-prod-analysis</string>
</dict>
</plist>
```
.png){kind=logo}
Hi @ARMFBTech (Community Member),
there is a chance that there is more information in the Flaw Details. You can expand the Flaw Details of a particular flaw by going to the Triage Flaws view in the Veracode Platform and clicking on the black arrow.
If your `Info.plist` file does not contain any information that is security-sensitive for your use case, you may want to propose a mitigation for the finding and discuss it with your organization's Security Team. For more information on how to propose a mitigation, please refer to https://docs.veracode.com/r/improve_mitigation.
Thank you,
Florian Walter