Use environment variables, configuration files, or similar methods to configure the IP address instead of hard-coding it. If confidentiality isn’t required, prefer a domain name to allow destination changes without rebuilding the software.
// Test file: pass.swift// Expected annotations: 0importFoundation// Compliant: IP is loaded from a configuration objectletprimaryServer=configuration.serverIp// Exception: IPv4 loopback address for local developmentletlocalServer="127.0.0.1"// Exception: IPv4 documentation address from RFC 5737lettestNetServer="198.51.100.50"// Exception: IPv6 documentation address from RFC 3849letipv6Example="2001:db8:85a3::8a2e:370:7334"// A version number that looks like an IP but fails the validationletappVersion="Application version 3.1.123.900 is not an IP."
Seamless integrations. Try Datadog Code Security
Datadog Code Security
Try this rule and analyze your code with Datadog Code Security
How to use this rule
1
2
rulesets:- swift-security # Rules to enforce Swift security.
Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Security scans to your CI pipelines