I don't see a way of doing this. The only options that you have are inside,outside, and management interfaces for the "logging host" command. This tells the ASA what interface to send the traffic out of when logging to a syslog server. Is this what you're wanting to log to?
You can log everything by an acl applied to an interface, and you can do that on an ASA as well. You append the log keyword at the end of the ACE. The problem is that if you aren't logging the traffic somewhere, then the buffer in the router/ASA will fill up and eventually overwrite. You'll have no way of going back once that happens.
If you are logging to a syslog server, you won't be able to selectively choose what messages are logged unless you filter (all messages are logged by default per severity level and down), and your ACL traffic will be logged as well. This is where a good management system comes in to be able to search your logs. If they just want traffic on this interface, maybe you should look into Websense (quite expensive), or place some sort of IDS to just log traffic in and out of that interface. Either way, they'll still need to have something to be able to search what data they're looking for.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...