# Restrict the access to some file operations (Implemented through clispec)

**URL:** https://dmap-community.ductus.global/t/restrict-the-access-to-some-file-operations-implemented-through-clispec/4414
**Category:** YANG
**Created:** [April 18, 2023, 4:12am UTC](https://dmap-community.ductus.global/t/restrict-the-access-to-some-file-operations-implemented-through-clispec/4414 "2023-04-18T04:12:39Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![sneha](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@sneha](https://dmap-community.ductus.global/u/sneha)
#### Post date: [April 18, 2023, 4:12am UTC](https://dmap-community.ductus.global/t/restrict-the-access-to-some-file-operations-implemented-through-clispec/4414/1 "2023-04-18T04:12:39Z")

</div>

Hi All,  
We have implemented some file operations like ‘file show/tail’ using clispec. But now we want to restrict the access to this operations for specific group users.

The NACM rule I added:

```
  <cmdrule xmlns="http://tail-f.com/yang/acm">
    <name>file-show</name>
    <command>file show</command>
    <access-operations>read exec</access-operations>
    <action>deny</action>
  </cmdrule>

```

I tried with adding above NACM cmdrule for specific group, to achieve the above requirement, but is there any other, more efficient way to fulfill this?

---

<div class="post-metadata">

### Author: ![mvf](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/mvf/32/182_2.png) [@mvf](https://dmap-community.ductus.global/u/mvf)
#### Post date: [April 18, 2023, 3:06pm UTC](https://dmap-community.ductus.global/t/restrict-the-access-to-some-file-operations-implemented-through-clispec/4414/2 "2023-04-18T15:06:23Z")

</div>

When you write “more efficient”, what do you mean, why is this not efficient enough?