Site Shield

List all of your Site Shield maps to make sure your maps are up to date, find a list of CIDRs to verify against your origins or firewall, or filter responses for acknowledgement information and status.

Get all maps

To get a list of your Site Shield maps, use the List-SiteshieldMaps command.

List-SiteshieldMaps
acknowledgeRequiredBy : 1679661685000
acknowledged : False
acknowledgedBy : jsmith
acknowledgedOn : 1649661984000
contacts : {example@example.com}
currentCidrs : {123.456.789.0/24, 134.56.789.0/24, 145.678.901.0/24, 178.901.234.0/24…} 
id : 123456789
latestTicketId : 2456
mapAlias : example
mcmMapRuleId : 12345
proposedCidrs : {101.102.103.0/24, 104.15.106.0/24, 107.108.109.0/24, 111.222.333.0/24‚Ķ} ruleName : ss.‚Äčakamai.‚Äčnet
service : S
shared : False
sureRouteName : route.name.example.com
type : Production

acknowledgeRequiredBy : 1679661685000
acknowledged : False
acknowledgedBy : jsmith
acknowledgedOn : 1649663984000
contacts : {example@example.com}
currentCidrs : {101.102.103.0/24, 104.15.106.0/24, 107.108.109.0/24, 111.222.333.0/24…} 
id : 987654321
latestTicketId : 1234
mapAlias : mymap
mcmMapRuleId : 23456
proposedCidrs : {101.102.103.0/24, 104.15.106.0/24, 107.108.109.0/24, 111.222.333.0/24‚Ķ} ruleName : ss.‚Äčakamai.‚Äčnet
service : S
shared : False
sureRouteName : route.name.example.com
type : Production
...

Get map by ID

Once you have a list of your maps, you can get a specific map by its ID.

Get-SiteshieldMapByID -SiteshieldID 123456789
acknowledgeRequiredBy : 1679661685000
acknowledged : False
acknowledgedBy : jsmith
acknowledgedOn : 1649661984000
contacts : {example@example.com}
currentCidrs : {123.456.789.0/24, 134.56.789.0/24, 145.678.901.0/24, 178.901.234.0/24…} 
id : 123456789
latestTicketId : 2456
mapAlias : example
mcmMapRuleId : 12345
proposedCidrs : {101.102.103.0/24, 104.15.106.0/24, 107.108.109.0/24, 111.222.333.0/24‚Ķ} ruleName : ss.‚Äčakamai.‚Äčnet
service : S
shared : False
sureRouteName : route.name.example.com
type : Production

Get map property by filter

Because the list all response truncates the full list of current and proposed CIDRs, get a complete list of CIDRs, or any other specific property, by piping directly to the object name.

# Get all proposed CIDRs. Here the get map was set to a variable named $Maps
$Maps[0].proposedCidrs

# Get map by alias
List-SiteshieldMaps | where mapAlias -eq mymap 
# Complete list of proposedCIDRs
101.102.103.0/24
104.15.106.0/24
107.108.109.0/24
111.222.333.0/24
102.103.104.0/24
105.16.107.0/24
108.109.111.0/24
112.333.444.0/24

# Get map by alias
acknowledgeRequiredBy : 1679661685000
acknowledged : False
acknowledgedBy : jsmith
acknowledgedOn : 1649663984000
contacts : {example@example.com}
currentCidrs : {101.102.103.0/24, 104.15.106.0/24, 107.108.109.0/24, 111.222.333.0/24…} 
id : 123456789
latestTicketId : 1234
mapAlias : mymap
mcmMapRuleId : 23456
proposedCidrs : {101.102.103.0/24, 104.15.106.0/24, 107.108.109.0/24, 111.222.333.0/24‚Ķ} ruleName : ss.‚Äčakamai.‚Äčnet
service : S
shared : False
sureRouteName : route.name.example.com
type : Production

Acknowledging Maps

As your traffic grows, we'll send you requests to update your current CIDRs. Acknowledging your Site Shield map(s) is a necessary step you should do within a few weeks of an available update.

We'll never add any new CIDRs without your acknowledgement, but we will remove them at a subnet's retirement from the network.

Because of this, if you leave things long enough, you can end up with a Site Shield map that contains a very small number of servers. This can affect performance and result in your site crashing.

To acknowledge you received and want to promote and use the proposed CIDRs, use the Acknowledge-SiteShieldMapByID command to promote them to current.

Acknowledge-SiteShieldMapByID -SiteshieldID 123456789
acknowledged = true
acknowledgedBy = jsmith
acknowledgedOn = 1673639894663
contacts = {example@example.com}
currentCidrs = {101.102.103.0/24, 104.15.106.0/24, 107.108.109.0/24, 111.222.333.0/24, 102.103.104.0/24, 105.16.107.0/24, 108.109.111.0/24, 112.333.444.0/24}
id = 123456789
latestTicketId = 23308
mapAlias = shared-enhanced
mcmMapRuleId = 23456
proposedCidrs = []
ruleName = s1234.akamaiedge.net
service = S
shared = false
sureRouteName = route.name.example.com
type = Production
Acknowledging a Site Shield map lets us know we need to start using new CIDRs to communicate with your origin.

We won't know if those CIDRs are allowlisted at your origin.


Before you acknowledge a map:

  1. Make a list of all origins in all properties using the Site Shield map.

    $Query = '$..behaviors[?(@.name=="siteShield")].options.ssmap[?(@.value=="s123.akamai.net")]'
    $Search = New-BulkSearch -Match $Query -Synchronous
    $Search.Results.PropertyName
    
  2. Get the list of proposed CIDRs from the Get-SiteshieldMapByID or List-SiteshieldMaps command.
  3. Update your firewall on all origins using the map to include the new CIDRs.
  4. Check your firewalls.
  5. Check your firewalls again.
  6. If required, ask your Akamai representatives if they can run some tests to ensure the new CIDRs are allowlisted.
  7. Acknowledge your map to promote proposed CIDRs to current.