Nope, as far as I know there is no document, but by default, the ASA will permit everything from inside going to outside (and the return traffic for the connection), but nothing from outside going to inside.
Since every company have different security policies, there is no way to create an standard of what is allowed and what not. There are some special RFCs that talk about special IP addresses that need to be blocked, but as far as I know, nothing that Cisco have created.
A more restrictive security posture is 'ALWAYS' good practice! The only thing you have to keep in mind, is if you internet gateway (in this case your ASA) is used for connections from your internal networks need to communicate directly with other hosts in the cloud you will need to poke holes for that traffic as well. Thanks.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...