> # About Crypto Map Entries

> Once you have created the crypto IPv4-ACLs and transform sets, you can create crypto map entries that combine the various parts of the IPsec SA, including the following:

> - The traffic to be protected by IPsec (per the crypto IPv4-ACL). A crypto map set can contain multiple entries, each with a different IPv4-ACL.
> - The granularity of the flow to be protected by a set of SAs.
> - The IPsec-protected traffic destination (who the remote IPsec peer is).
> - The local address to be used for the IPsec traffic (applying to an interface).
> - The IPsec security to be applied to this traffic (selecting from a list of one or more transform sets).
> - Other parameters to define an IPsec SA.

> Crypto map entries with the same crypto map name (but different map sequence numbers) are grouped into a crypto map set.

> When you apply a crypto map set to an interface, the following events occur:

> - A security policy database (SPD) is created for that interface.
> - All IP traffic passing through the interface is evaluated against the SPD.

> If a crypto map entry sees outbound IP traffic that requires protection, an SA is negotiated with the remote peer according to the parameters included in the crypto map entry.

> The policy derived from the crypto map entries is used during the negotiation of SAs. If the local switch initiates the negotiation, it will use the policy specified in the crypto map entries to create the offer to be sent to the specified IPsec peer. If the IPsec peer initiates the negotiation, the local switch checks the policy from the crypto map entries and decides whether to accept or reject the peer's request (offer).

> For IPsec to succeed between two IPsec peers, both peers' crypto map entries must contain compatible configuration statements.

> Copyright 2010-2015, Cisco Systems, Inc. All rights reserved.